Changes between Version 61 and Version 62 of TracQuery

Timestamp:

May 27, 2022, 11:32:00 PM (23 months ago)

Author:

figaro

Comment:

Standardise permission styling

TracQuery

@@ -44 +44 @@
 You can also save references to queries in Wiki content, as described below.
 
-'''Note:''' one way to easily build queries like the ones below is to create and test the queries using Custom Query module. Clicking ''Save query'' will display the query string for you, all you need to do is remove the extra line breaks.
+'''Note:''' One way to easily build queries like the ones below is to create and test the queries using Custom Query module. Clicking ''Save query'' will display the query string for you, all you need to do is remove the extra line breaks.
 
-'''Note:''' you must have the '''REPORT_CREATE''' permission in order to save queries to the list of default reports. The ''Save query'' button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.
+'''Note:''' You must have the `REPORT_CREATE` permission to save queries to the list of default reports. The ''Save query'' button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.
 
 == TracLinks to Queries
@@ -52 +52 @@
 You can make a link to a query from any Wiki page using a simple [TracQuery#QueryLanguage query language] to specify the criteria.
 {{{
-[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
+[query:status=new|assigned|reopened&version=1.4 Active tickets against 1.4]
 }}}
 
 Which is displayed as:
-  [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
+  [query:status=new|assigned|reopened&version=1.4 Active tickets against 1.4]
 
 Alternatively, you can copy the query string from the browser URL box and paste it into the Wiki link, including the leading `?` character:
@@ -98 +98 @@
 
 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=2007-01-01..2008-01-01`''' || query tickets created in 2007 ||
+|| '''`created=2017-01-01..2018-01-01`''' || query tickets created in 2017 ||
 || '''`created=lastmonth..thismonth`''' || query tickets created during the previous month ||
 || '''`modified=1weekago..`''' || query tickets that have been modified in the last week ||