I have assumed the answer is in Custom Search and have read that help
many times, but have been unable to figure out how use it for this
The search needs to identify bugs with dependencies ("Depends on" is not
empty), then look at the "Status" of each of those blocker bugs (this
latter part is what I haven't figured out). Can you help with that?
On 22/08/2017 18:19, Thorsten Schöning wrote:
> Get all bugs which are resolved, do
> block others and in the search results there's a column "Blocks" with
> a list of all bugs blocked by a particular bug. Those should be the
> results your are looking for.
This does not give the desired result because it noes not filter on the
status of bugs in the "Blocks" column.
If one views an individual bug, the status of Dependant and Blocker bugs
is shown - resolved bugs are shown struck-through. In a list view the
Dependant and Blocker bugs can be shown, but their status is not. I was
trying to create a query that worked around that shortcoming.
>> I wish to find bugs which no longer have any unresolved dependant bugs.
> This is about the status of "the other" bugs, not the bugs you are
> interested in. You are interested in bugs which are blocking others and
> those others need to have some special status.
>> The search needs to identify bugs with dependencies ("Depends on" is not
>> empty), then look at the "Status" of each of those blocker bugs (this
>> latter part is what I haven't figured out).
> This on the other side is about the status of the bugs your are
> interested in, those which are blocking, and therefore from my
> understanding different to your first question.
I still think both of my questions are consistent; your mind-reading
seems to be failing you. :-)
Let's approach this by way of a specific but arbitrary example.
On 23/08/17 22:44, Dale Rebgetz wrote:
> Look at the first record - 13168. It has two dependants: 36665 and
> 48322. The first has been resolved, but not the second. Therefore it is
> not possible to close 13168.
> Look at the second record - 26291. It has one dependant: 76944. That has
> been resolved so it is possible to close 26291.
> I would like to be able to modify the above search to exclude 13168 but
> include 26291.
Yes, your question is quite clear, thank you :-)
I believe the answer is that this sort of query is not possible using
Bugzilla's standard interface. You would need to write a small program
to query the API for the search that you have given us, and then to get
the status of all of the bugs in the dependency lists and filter the
results accordingly, then provide the results to the user.
The other option would be to customize Bugzilla to add a checkbox to the
search interface which added a clause to the SQL query which achieved
what you wanted.
I apologise that this is probably not the answer you were looking for.
On 25/08/2017 0:34, Gervase Markham wrote:
> I believe the answer is that this sort of query is not possible using
> Bugzilla's standard interface.
Thanks. That is what I needed to know - that I should not waste any more
time trying to create such a query with the custom search interface.
What ideally I would like to see is search results showing the status of
"Depend on" and "Blocks" in the same way that is already done when
viewing individual bugs. i.e. dependant and blocker bugs that are
resolved are shown struck-through.