Current blueprint isn't "in grey" even if it's been implemented
Bug #121830 reported by
Matthew Paul Thomas
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
1. Register a blueprint.
2. Make it dependent on another blueprint.
3. Change the blueprint's status to "Implemented".
4. Observe the dependency tree, with its text "Specifications in grey have been implemented".
What you see: The current blueprint is white with a red border.
What's wrong with this: "Specifications in grey have been implemented" is technically correct, because that all grey blueprints have been implemented does not necessarily mean that all implemented blueprints are grey. However, it is still misleading.
What you should see: Either the current blueprint is "in grey", or the caption is updated.
See also bug 58784.
Changed in blueprint: | |
status: | New → Confirmed |
Changed in blueprint: | |
importance: | Undecided → Low |
status: | Confirmed → Triaged |
To post a comment you must log in.