Bug 1808906

Summary: RFE: Add a timebox to status comparisons in advanced search
Product: [Community] Bugzilla Reporter: Brendan Conoboy <blc>
Component: Query/Bug ListAssignee: PnT DevOps Devs <hss-ied-bugs>
Status: CLOSED DEFERRED QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.0CC: khong, liyu, meli
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-02 04:08:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brendan Conoboy 2020-03-01 23:35:10 UTC 
The advanced search feature of bugzilla allows searching for status changes and it allows for time boxing of date fields, but it lacks the ability to narrow results to a time box around status changes.  Having the ability to query when a transition happened would be very useful.  Something like:

( ( Status | changed from | NEW ) && before -7d )

  or

( ( Status | changed to | MODIFIED ) && after -7d )

Basically looking for an extension to the "changed XXX" searches to add a time bound.  Should basically work with the facts stored in the status change table.  It could be applied to a single search, or to a group inside a parenthesis.
Comment 1 Jeff Fearn 🐞 2020-03-02 01:01:19 UTC 
I think you can already do this if you use enough parenthesis.

https://bugzilla.redhat.com/query.cgi?bug_status=VERIFIED&bug_status=RELEASE_PENDING&f1=OP&f2=OP&f3=bug_status&f4=bug_status&f5=CP&f6=OP&f7=bug_status&f8=bug_status&f9=CP&j2=AND_G&j6=AND_G&list_id=10879055&o3=changedbefore&o4=changedfrom&o7=changedafter&o8=changedto&product=Red%20Hat%20Enterprise%20Linux%208&query_format=advanced&v3=-7d&v4=NEW&v7=-7d&v8=MODIFIED

Note that the example give is an enormous search space so might time out if you include CLOSED or even NEW bugs.

The first date is < now -7days, which is a all the way back to when b.r.c started.

It might be worth testing with this as a base to see if it does give you the results you want.
Comment 2 Brendan Conoboy 2020-03-02 04:08:34 UTC 
It looks like that "against the same field" selector option is doing the trick.  It's slightly more granular than I was hoping for, but I can work with it.  Thanks!