Closed Bug 114402 Opened 23 years ago Closed 20 years ago

Put legal date format by "During dates" in query page.

Categories

(Bugzilla :: Query/Bug List, enhancement)

2.10
enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 98990

People

(Reporter: cote, Assigned: nobody)

References

()

Details

I enter a query by date and I add a message saying that the format I used for
that was illegal.

I think the source of the query page should be modify to display what is the
legal bug format, with a string like

yyyy-mm-dd

Similaily, the error message should also contains a String with a similar format.
Summary: What a legal bug format → What a legal date format for a bug
Target Milestone: --- → Bugzilla 2.18
It wasn't clear for me either, but after looking at "Now" for a while I tried
entering "Last month" for the heck of it and that worked. So valid format is
"Last [month|week|day]" etc methinks.

Some info on the error page would be nice though.
Um, nevermind. I forgot to select a field. ^^;
From http://bugzilla.mozilla.org/queryhelp.cgi (the clue link at the top of the
Query form):

During dates [text] to [text]

Here, you can choose what dates the fields changed. "Now" can be used as an
entry. Other entries should be in mm/dd/yyyy or yyyy-mm-dd format.


This bug now looks like an enhancement to me.
OS: Windows NT → All
Hardware: PC → All
Changing the severity to enh. Changing summary to more meaningful.
This could be solved, if instead of "Now", today's date was filled in one of the
legal formats as "end date" automatically.
Severity: normal → enhancement
Summary: What a legal date format for a bug → Put legal date format by "During dates" in query page.
I am looking at the query page of version 2.17.1 of Bugzilla, and that seem to
be there.

http://bugzilla.mozilla.org/query.cgi

Can I close this bug as fixed.
Assignee: endico → nobody
Enhancements which don't currently have patches on them which are targetted at
2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. 
Consideration will be taken for moving items back to 2.18 on a case-by-case
basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
WFM per comment 5.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---

*** This bug has been marked as a duplicate of 98990 ***
Status: REOPENED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → DUPLICATE
clearing target of DUPLICATE/WONTFIX/INVALID/WORKSFORME so they'll show up as
untriaged if they get reopened.
Target Milestone: Bugzilla 2.22 → ---
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.