177697 - More date options needed in queries.

Status: VERIFIED DUPLICATE of bug 149246

(Bugzilla :: Query/Bug List, enhancement)

Description

[Jason Bassford]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021028
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021028

In a BMO query I can easily get a report of bugs that have been fixed in the
past 24 hours.  (Resolution: Fixed, Only bugs where any of the fields:
resolution, and were changed between: 10/30/2002 and Now.)

However, I always have to manually input yesterday's date.  As far as I can tell
there's no method by which I can have this done automatically.  Entering
"Yesterday"  and "Now" does not work, nor does something like "Now-1" and "Now"
get validated.

I would like to have some method by which I can set up a query that will always
give me the bugs that have been resolved FIXED in the last 24 hours.  There
should be more than just between [manually entered date] and Now available.

Note that using the already existing "Only bugs changed in the last [ ] days"
does not work because it is not additive with the following "Only bugs where any
of the fields" criteria.  Perhaps it should be.

Reproducible: Always

Steps to Reproduce:
1. Try to use the Bugzilla query to create a link that will always give bugs
FIXED in the past 24 hours, regardless of the current date.
Actual Results:  
You can't.

Expected Results:  
There should be some method of accomplishing this.

Comment 1

[Jason Bassford]

Changing Summary to better reflect what I'm getting at here.

Comment 2

[Jeff Hedlund]

Along these same lines, I'd like to be able to run a query that includes all the
days since I last ran the query.

Comment 3

[Jason Bassford]

> I'd like to be able to run a query that includes all the
> days since I last ran the query.

Only theoretically possible if BMO logs all of our queries.  I doubt that it
does, or that such a suggestion would be anything other than WONTFIX due to the
database space this would take up. 

Comment 4

[Jeff Hedlund]

> Only theoretically possible if BMO logs all of our queries.  I doubt that it
> does, or that such a suggestion would be anything other than WONTFIX due to the
> database space this would take up. 

No, I'm thinking of a saved query, so it wouldn't take much space.  Could be
done with an extra field that hold a datestamp of the date the query was last run.

Comment 5

[Matt McHenry]

This sounds like (mostly) a dupe of bug 37749.

Comment 6

[Ran]

I run a query for all bugs changed in the past 0 (zero) days.  If you set to
bugs resolved fixed -- that should approximate the behavior you're looking for.

Comment 7

[Jason Bassford]

I don't see how bugs changed in the past 0 days (?) helps here.  I'm talking
about bugs fixed in the past X days, where I don't need to specify a MM/DD/YY
date but just a number of days.

BTW: Bug 37749 is all about bugs FILED / CREATED in the past X days, not about
bugs who's resolution has changed to FIXED, etc., in the past X days.

Comment 8

[Jason Bassford]

Doh!  But thanks to bug 37749 comment 26, I now know that relative dates were
made available with the fix for bug 149246.  But there were NEVER documented, so
there was no way I could have known about this.

To report all bugs fixed in the past X days:

Resolution FIXED, only bugs where resolution were changed between "Xd" and "Now"
to value FIXED.

Since bug 149246 was checked in PRIOR to the opening of this bug, I'm (after
almost 3 months) going to mark this bug INVALID.

Typical.  (It would have been nice if documentation had been provided for bug
149246 ealier and/or if somebody familiar with Bugzilla had spotted this bug and
commented on it.)

Comment 9

[Jason Bassford]

Reopening.

Mid-air collision with myself somehow.  (Do not ask - I don't know what
happened.)  I changed my mind as to the correct resolution.

Comment 10

[Jason Bassford]

This is really a (belated) dupe of bug 149246.

Note: Getting a query from the last time a query was run should be a new bug.

*** This bug has been marked as a duplicate of 149246 ***

Comment 11

[Jason Bassford]

Verifying resolution of all bugs I've reported.