Changes between Version 2 and Version 3 of TracQuery


Ignore:
Timestamp:
22/02/2023 10:14:46 (21 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracQuery

    v2 v3  
    4343You can also save references to queries in Wiki content, as described below.
    4444
    45 '''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.
     45'''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.
    4646
    47 '''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.
     47'''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.
    4848
    4949== TracLinks to Queries
    … …  
    5151You can make a link to a query from any Wiki page using a simple [TracQuery#QueryLanguage query language] to specify the criteria.
    5252{{{
    53 [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
     53[query:status=new|assigned|reopened&version=1.4 Active tickets against 1.4]
    5454}}}
    5555
    5656Which is displayed as:
    57   [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
     57  [query:status=new|assigned|reopened&version=1.4 Active tickets against 1.4]
    5858
    5959Alternatively, you can copy the query string from the browser URL box and paste it into the Wiki link, including the leading `?` character:
    … …  
    6767== Query Language
    6868
    69 The `query:` TracLinks and the [TicketQuery "[[TicketQuery]]"] macro both use a mini “query language” for specifying query filters. Filters are separated by ampersands (`&`). Each filter consists of the ticket field name, an operator and one or more values. Multiple values are separated using a pipe (`|`), meaning the filter matches any of the values. To include a literal `&` or `|` in a value, escape the character with a backslash (`\`).
     69The `query:` TracLinks and the [TicketQuery "[[TicketQuery]]"] macro both use a mini “query language” for specifying query filters. Filters are separated by ampersands (`&`), the `[[TicketQuery]]` macro additionally also accepts commas (`,`). Each filter consists of the ticket field name, an operator and one or more values. Multiple values are separated using a pipe (`|`), meaning the filter matches any of the values. To include a literal `&` or `|` in a value, escape the character with a backslash (`\`).
    7070
    7171The available operators are:
    … …  
    8181|| '''`!$=`''' || the field content does not end with any of the values ||
    8282
    83 Filters combining matches and negated matches can be constructed for text fields such as Keywords and CC using the //contains// (`~=`) operator. The `-` operator is used to negate a match and double quotes (//since 1.2.1//) are used for whitespace-separated words in a phrase. For example, `keywords~=word1 word2 -word3 "word4 word5"` matches tickets containing `word1` and `word2`, not `word3` and also `word4 word5`.
     83Filters combining matches matches can be constructed for text fields such as Keywords and CC using the //contains// (`~=`) operator.
     84The `!` operator is used to negate a match.
     85
     86Note that for `query:` the match operator `=` needs to be on first position when combined with other operators, for example `=!` or `=~`. The `[[TicketQuery]]` macro on the other side accepts both syntax variants, for example `!=` or `~=` as well as `=!` or `=~`.
     87
     88Double quotes (//since Trac 1.2.1//) are used for whitespace-separated words in a phrase. For example, `keywords~=word1 word2 -word3 "word4 word5"` matches tickets containing `word1` and `word2`, not `word3` and also `word4 word5`.
     89
    8490|| '''`status=closed,keywords~=firefox`''' || query closed tickets that contain keyword `firefox` ||
    8591|| '''`status=closed,keywords~=opera`''' || query closed tickets that contain keyword `opera` ||
    … …  
    9197
    9298The 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.
    93 || '''`created=2007-01-01..2008-01-01`''' || query tickets created in 2007 ||
     99|| '''`created=2017-01-01..2018-01-01`''' || query tickets created in 2017 ||
    94100|| '''`created=lastmonth..thismonth`''' || query tickets created during the previous month ||
    95101|| '''`modified=1weekago..`''' || query tickets that have been modified in the last week ||