You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Brian Federle (JIRA)" <ji...@apache.org> on 2013/07/22 19:56:51 UTC
[jira] [Resolved] (CLOUDSTACK-3153) [UI] Network ACL : Incorrect
API calls when changing the rule number
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Federle resolved CLOUDSTACK-3153.
---------------------------------------
Resolution: Unresolved
Assignee: Kishan Kavala (was: Brian Federle)
I'm still of unsure of what to do in the situation though if the user drags the row to a certain position, and the rest of the rows are numbered incrementally. i.e., 1, 2, 3, 4. Clearly if we didn't change the numbering of the rest of the rows and picked an unused number (such as 5), then the row we dragged would be a the top of the priority list, which isn't what we wanted. Wouldn't we have to change the numbering of the rest of the rows in this situation? I know we can fix this by manually changing the rule number via the edit screen, but this would defeat the purpose of the drag-and-drop.
Also please post the URL AWS reference docs into this but so I can take a look at it.
> [UI] Network ACL : Incorrect API calls when changing the rule number
> --------------------------------------------------------------------
>
> Key: CLOUDSTACK-3153
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3153
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: UI
> Affects Versions: 4.2.0
> Reporter: Kishan Kavala
> Assignee: Kishan Kavala
> Priority: Critical
> Fix For: 4.2.0
>
>
> After creating Network ACL rules, UI for changing the number is not correct.
> UI should just update the number of rule that is moved. It should be a single updateNetworkACL API call.
> UI currently fires 2 APIs and both of them fail. UI should not try to swap the numbers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira