yahoo-eng-team team mailing list archive

[Chuck Short <chuck.short@xxxxxxxxxxxxx>]

** Also affects: horizon/icehouse
   Importance: Undecided
       Status: New

** Changed in: horizon/icehouse
    Milestone: None => 2014.1.2

** Changed in: horizon/icehouse
       Status: New => Fix Released

** Changed in: horizon/icehouse
       Status: Fix Released => Fix Committed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1326132

Title:
  Adding a new Security Rule to a Security Group shouldn't remove the
  sort on the table

Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in OpenStack Dashboard (Horizon) icehouse series:
  Fix Committed

Bug description:
  If I'm manually adding security rules to a security group, I don't
  think it's unreasonable for me to have the table sorted on Port or
  Protocol while I'm building out the group, but if I have the table
  sorted, each time you add a new rule, it reverts to the default sort
  of the table. (Side question, how is the table sorted by default? It
  doesn't appear to be port or direction or protocol, or ether type, or
  remote, or even when the rule was created. It just looks like a
  jumbled mess, hence why I want to keep it sorted...)

  If I have the table sorted on Port, so I can keep track of which ones
  I've added already easily, it would be great if Horizon was smart
  enough to keep the sort applied, and just add the new rule, rather
  than forcing me to resort the table again, click add, create the rule,
  sort the table again, etc etc.

  It would also be nice if there was a table sort indicator, but that's
  probably a topic for another bug :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1326132/+subscriptions