Closed Bug 97947 Opened 24 years ago Closed 24 years ago

Need a way to match multiple conditions on the same attachment

Categories

(Bugzilla :: Query/Bug List, defect)

2.15
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 99716

People

(Reporter: justdave, Assigned: endico)

References

Details

Here's the current situation... I wanted to set up a query that would look for patches that are waiting for review without depending on people to set the patch keyword. What obviously made sense was to use the boolean chart and set up a query like this: attachment is patch is equal to 1 attachment is obsolete is equal to 0 attachment status does not contain needs-work the problem with this is that it performs each of those matches individually on every attachment on the entire bug. Which means that if I have two patches on a bug, and the first one has the obsolete flag set, but is not marked needs-work, and the second patch has the needs-work flag set, but is not marked obsolete, then that bug will match this query, even though neither of the attachments meets all three conditions. Maybe we need a section of the advanced query page for "search for bugs with attachments that match these conditions" and have checkboxes for patch and obsolete, a list box for the statuses (with a checkbox for "any status except the ones selected"), and edit boxes for description and mime type (with the usual popup menus for how to compare the strings)...
Depends on: 99716
I know you all know more about this than I do but here's what it looks like to me. This should work like a boolean chart query for comments or any other field which can occur multiple times in a report. If you use AND, rather than Add antother chart, then it should find matches when they all apply to the same occurence of the field.
over to myk. *** This bug has been marked as a duplicate of 99716 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.