qa-needstesting revisions should not be greyed out
Bug #688073 reported by
Aaron Bentley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| qa-tagger |
Triaged
|
Low
|
Unassigned | ||
Bug Description
revisions falling after a revision that cannot be deployed are greyed out and hard to read. But for a release manager trying to ensure that a batch of revisions gets QAed, it should be easy to determine which revisions need to be QAed. So they should not be greyed out.
It would be nice to split this out into a separate "revisions needing QA" list. Even better if it listed both "qa-needstesting" and qa-bad revisions that haven't been fixed.
Revision history for this message
| Aaron Bentley (abentley) wrote | #1 |
| tags: | added: deployment-qa |
| Changed in qa-tagger: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Robert Collins (lifeless) wrote | #2 |
| Changed in qa-tagger: | |
| importance: | High → Low |
| tags: | added: easy |
To post a comment you must log in.
I can imagine the grey being hard to read; a simple fix would be to reduce the fade a little. That said, this is more of an itch-scratching issue than a deep problem, as we're operating ok with the status quo.