Description of problem:
Bugzilla should highlight ON_QA bugs, and differ ones which have unverified/closed dependencies.
It would be so helpful to notice quickly which bugs needs to be verified from the blocked ones.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
It's not entirely clear to me what you're asking for. Bugzilla has two dependency views:
1. A graph view, which uses different colours for open and closed bugs (see example at https://bugzilla.redhat.com/showdependencygraph.cgi?id=653316)
2. A tree view, which includes the status of each bug and has strikethrough to highlight closed bugs (see example at https://bugzilla.redhat.com/showdependencytree.cgi?id=653316). This view also has a "Hide Resolved" button that you can use to filter closed bugs out of the view.
If neither of these views provides the information you need, please state which view you are refering to and exactly what you would like the Bugzilla Team to change in that view.
Please keep in mind however that the majority of Red Hat Bugzilla users are not in QE roles, so highlighting only ON_QA bugs in any view may not be satisfactory for many users.
Created attachment 924893 [details]
Jason,I've added an image,hopefully it will make things clearer.
I'm merely suggesting that when a user query his ON_QA bugs there will be some kind of sign that will differ ON_QA bugs which are dependent on existing bugs(and there for cannot be verified yet) to ON_QA bugs which can be(and needs to be) verified right away.
it can be a text highlight,red dot or any kind of icon.
right now engineers are entering each bug and look at the dependency tab and than browse back if they see dependency etc.
This RFE will save tons of time and could be very neat also.
Ok, I think that makes the use-case clearer. Please confirm that the following understanding is correct:
(a) The attachment is a mockup, not a screenshot of what Bugzilla does now. (BTW, we made the attachment private as it contains data about private bugs).
(b) You're asking for a change to buglist.cgi rather than to the Dependency Tree or Dependency Graph pages.
(c) An ON_QA bug can only be tested by an engineer if all of its blockers are in VERIFIED, RELEASE_PENDING or CLOSED.
Bug 1135866, when implemented, may help to alleviate this issue. The user will be able to add the "Depends On (full)" column to buglist.cgi and see the status of each dependency in a tooltip.
(In reply to Jason McDonald from comment #5)
> Bug 1135866, when implemented, may help to alleviate this issue. The user
> will be able to add the "Depends On (full)" column to buglist.cgi and see
> the status of each dependency in a tooltip.
Except 1: there is no tool tip, 2: the standard classes applied to bug links are missing (e.g.bz_status_CLOSED), so closed bugs don't have strike through applied.
(In reply to Jeff Fearn from comment #6)
> Except 1: there is no tool tip, 2: the standard classes applied to bug links
> are missing (e.g.bz_status_CLOSED), so closed bugs don't have strike through
Bug 1267819 filed to track those issues.
Color coding like this for deps is already in 5.0, may as well get it QE'd properly.
BZ5 could highlight ON_QA bugs,but it couldn't differ ones which have dependencies from one who doesn't.
All verify status bugs are in same color.
(In reply to Rony Gong from comment #10)
> BZ5 could highlight ON_QA bugs,but it couldn't differ ones which have
> dependencies from one who doesn't.
> All verify status bugs are in same color.
You need to use the treeview to see the dependent bug statuses, there is no sane way to display nested status on a single dependency.
Tested on QA environment(5.0.3-rh3)
1. Do a bug search(some bugs has dependent bugs), then click the button 'TreeView+ (depend on)' in the bottom of bug list page.
2. In the tree view page, please click the 'Expand All'link, then you could go though all depend bugs' status easily.