1543984 - Allow to search on last change date

Status: NEW

(bugzilla.mozilla.org :: Search, enhancement)

Description

[Calixte Denizet (:calixte)]

Right now we can search for a field which has been "changed after" or "changed before".
It'd be nice to be able to search on last change to be able to have an information on the current state of the bug.
So for example, we could have:
f1: component,
v1: last_changedbefore,
o1: -2w

and it will return bugs where the component has been changed at least 2 weeks ago but not changed after.

Comment 1

[Kohei Yoshino [:kohei]]

Attachment: Custom Search

Apparently this can be done by using the “Not” checkbox like this.

Comment 2

[Calixte Denizet (:calixte)]

Yeah I know this workaround.
But let me show you a query I wrote to get bugs where product/component have changed between second and first (or not changed but created between second and first):
{
...
'j3': 'OR',
'f3': 'OP',
'j4': 'AND',
'f4': 'OP',
'n5': 1, # we use a negation here to be sure that no change after first
'f5': 'product',
'o5': 'changedafter',
'v5': first,
'f6': 'product', # here the bug has changed
'o6': 'changedafter',
'v6': second,
'n7': 1,
'f7': 'component',
'o7': 'changedafter',
'v7': first,
'f8': 'CP',
'j9': 'AND',
'f9': 'OP',
'n10': 1,
'f10': 'component',
'o10': 'changedafter',
'v10': first,
'f11': 'component',
'o11': 'changedafter',
'v11': second,
'n12': 1,
'f12': 'product',
'o12': 'changedafter',
'v12': first,
'f13': 'CP',
'j14': 'AND',
'f14': 'OP',
'f15': 'creation_ts',
'o15': 'lessthaneq',
'v15': first,
'f16': 'creation_ts',
'o16': 'greaterthan',
'v16': second,
'n17': 1,
'f17': 'product',
'o17': 'changedafter',
'v17': '1970-01-01',
'n18': 1,
'f18': 'component',
'o18': 'changedafter',
'v18': '1970-01-01',
'f19': 'CP',
'f20': 'CP',
}

my goal is just to get bugs which have been "triaged" between second and first.

Comment 3

[Kohei Yoshino [:kohei]]

Attachment: Custom Search 2

It look like this. I don’t fully understand the use case yet though.

The problem is the bug history is somewhat unreliable at this time. For example, products components are hardcoded as names, not as IDs, in the log. Even if this can be implemented, the “last changed” results might be wrong.

Comment 4

[Calixte Denizet (:calixte)]

The use case is to get bugs (defects) which have been triaged between 4 and 2 weeks ago with no priority set.

Comment 6

[Master ? [:masterquestionable]]

    [ Quote Calixte Denizet @ CE 2019-04-16 09:25:04 UTC:
https://bugzilla.mozilla.org/show_bug.cgi?id=1543984#c4
    ... to get bugs (defects) which have been triaged between 4 and 2 weeks ago with no priority set. ]
<^>    Should work, but may not:
    https://bugzilla.mozilla.org/query.cgi?format=advanced&bug_type=defect&j_top=OR&f1=OP&j1=AND_G&f2=bug_status&o2=changedafter&v2=-4w&f3=bug_status&o3=changedbefore&v3=-2w&f4=CP&f5=OP&j5=AND_G&f6=resolution&o6=changedafter&v6=-4w&f7=resolution&o7=changedbefore&v7=-2w&f8=CP&f9=OP&j9=AND_G&f10=priority&o10=changedafter&v10=-4w&f11=priority&o11=changedbefore&v11=-2w&f12=priority&o12=changedto&v12=--&f13=CP&f14=OP&f15=OP&j15=AND_G&f16=creation_ts&o16=greaterthan&v16=-4w&f17=creation_ts&o17=lessthan&v17=-2w&f18=CP&f19=priority&o19=equals&v19=--&f20=CP

    See [ https://bugzilla.mozilla.org/show_bug.cgi?id=1784601 ] for more details.