"Assignee: None" and "Tags: None" clutter bug listings
Bug #894734 reported by
Jonathan Lange
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When a bug has no assignees or no tags, and I'm looking at a customized bug listing that shows assignees and tags, then showing "Tags: None" or "Assignee: None" harms more than helps. It makes bugs that have no tags or no assignee look *more* similar to bugs that have tags and assignees. This means you get less information at first glance, because you need to read and think first. Web pages aren't supposed to make you think, are they?
| tags: | added: bug-columns |
| Changed in launchpad: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
Revision history for this message
| Bryce Harrington (bryce) wrote | #1 |
Revision history for this message
| Martin Pool (mbp) wrote | #2 |
To post a comment you must log in.
This is true and I agree.
I do see one benefit to the current behavior though - if you are scanning down the list looking at bug ages or reporters, currently they're all (roughly) in alignment. If you take out Assignee: None, then the reporter and age and other subsequent columns become jagged and not easy to scan.