Changes between Version 62 and Version 63 of TracQuery

Timestamp:

May 14, 2024, 10:14:48 AM (2 months ago)

Author:

Clemens

Comment:

Added some "natural date specifications" in section "Query Language". In particular it was not clear to me how to compose a future date, namely with keyword "in" (similar to "ago" for past dates). Note that future dates become important if you have a custom date field "due date" or similar.

TracQuery

@@ -97 +97 @@
 || '''`status=closed,keywords~=opera -firefox`''' || query closed tickets that contain keyword `opera`, but no `firefox` ||
 
-The date fields `created` and `modified` and custom fields of type `time` can be constrained by using the `=` operator and specifying a value containing two dates separated by two dots (`..`). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be omitted to avoid having to quote the query string.
+The date fields `created` and `modified` and custom fields of type `time` can be constrained by using the `=` operator and specifying a value containing two dates separated by two dots (`..`). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be omitted to avoid having to quote the query string.
 || '''`created=2017-01-01..2018-01-01`''' || query tickets created in 2017 ||
 || '''`created=lastmonth..thismonth`''' || query tickets created during the previous month ||