"focus of development" shown as another (incorrectly capitalised) series status
Bug #253534 reported by
William Grant
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
The development focus series of a project has its status shown as "focus of development". Of course, it is actually "Active Development".
It could at least be properly capitalised and maybe have a star like branches do. The darkened background makes it less obvious - it looks like a heading.
Related branches
lp://staging/~sinzui/launchpad/over-and-over
- Graham Binns (community): Approve (code)
-
Diff: 124 lines (+24/-8)6 files modifiedlib/lp/registry/browser/distroseries.py (+5/-2)
lib/lp/registry/browser/tests/distroseries-views.txt (+10/-0)
lib/lp/registry/interfaces/product.py (+4/-1)
lib/lp/registry/stories/product/xx-product-edit.txt (+2/-2)
lib/lp/registry/stories/productseries/xx-productseries-series.txt (+1/-1)
lib/lp/registry/templates/productseries-macros.pt (+2/-2)
Revision history for this message
| Matthew Paul Thomas (mpt) wrote | #1 |
| affects: | launchpad-foundations → launchpad-registry |
| Changed in launchpad-registry: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #2 |
| tags: | added: trivial |
| Changed in launchpad-registry: | |
| milestone: | none → series-10.05 |
| Changed in launchpad-registry: | |
| assignee: | nobody → Curtis Hovey (sinzui) |
| milestone: | series-future → 10.05 |
| status: | Triaged → In Progress |
Revision history for this message
| Ursula Junque (ursinha) wrote Bug fixed by a commit | #3 |
| Changed in launchpad-registry: | |
| status: | In Progress → Fix Committed |
| tags: | added: qa-needstesting |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad-registry: | |
| status: | Fix Committed → Fix Released |
| Changed in launchpad: | |
| assignee: | Curtis Hovey (sinzui) → nobody |
To post a comment you must log in.
Perhaps this should use the same highlight CSS class that the "Affects" table in bug reports does.