Introduce constants for volume status values

Bug #1355287 reported by Gary W. Smith
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Expired
Low
Unassigned

Bug Description

Volume status values ('available', 'error', etc) are hardcoded in various places throughout the UI. Constants should be introduced for these and used consistently throughout horizon.

Cindy Lu (clu-m)
Changed in horizon:
status: New → Triaged
importance: Undecided → Low
Changed in horizon:
assignee: nobody → Keisuke HANAMURA (k-hanamura)
Changed in horizon:
status: Triaged → In Progress
Revision history for this message
Akihiro Motoki (amotoki) wrote :

Clearing the assignee due to long inactivity.

In addition, the bug description does not refer to an example and various refactoring has been done since then.
The project and admin volume tables now share the status definitions, and it sounds reasonable that different resources have separate status definitions, so the status is unclear. Let's mark it as Incomplete.

Changed in horizon:
assignee: Keisuke HANAMURA (k-hanamura) → nobody
status: In Progress → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]

Changed in horizon:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.