Duplicated status colors in bug listings reduce visual differentiation
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
The custom bug listing feature uses colored backgrounds in the 'status' column to show different status values. The colors are the same for 'fix committed' and 'in progress', making it impossible to visually differentiate between the two states. I assume there is a desire to minimize the number of colors, but it seems strange to me that 'in progress' and 'fix committed' are deemed sufficiently similar to share the same color.
My use case is that we have a set of bugs in a project that needs to be fixed for release during a defined milestone. I want to see at a glance which bugs are fixed + waiting to be released vs. not fixed (new/confirmed/
| tags: | added: bug-columns |
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in launchpad: | |
| importance: | Low → High |
| Robert Collins (lifeless) wrote | #1 |
| Changed in launchpad: | |
| importance: | High → Low |
| summary: |
- Duplicated colors in bug listings make it impossible to visually parse - status + Duplicated status colors in bug listings reduce visual differentiation |
| Zygmunt Krynicki (zyga) wrote | #2 |
The design discussion around this during bug-columns was that we have more status values than semantic differences - see the IssueTracker proposal for a more comprehensive analysis of this. As such, we are moving to group and reduce the number of status values (but will take care to support workflows that need differentiation).
That said, this is deliberate - its not something that we want to change in isolation.