Changes between Version 2 and Version 3 of TracQuery
- Timestamp:
- Jul 25, 2013, 12:02:43 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracQuery
v2 v3 13 13 * If not logged and no name/email defined in the preferences then all open issues are displayed. 14 14 15 Current filters can be removed by clicking the button to the right with the minus sign on the label. New filters are added from the pulldown lists at the bottom corners of the filters box ('And' conditions on the left, 'Or' conditions on the right). Filters with either a text box or a pulldown menu of options can be added multiple times to perform an ''or'' of the criteria.15 Current filters can be removed by clicking the button to the left with the minus sign on the label. New filters are added from the pulldown lists at the bottom corners of the filters box ('And' conditions on the left, 'Or' conditions on the right). Filters with either a text box or a pulldown menu of options can be added multiple times to perform an ''or'' of the criteria. 16 16 17 17 You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket. … … 32 32 33 33 ''Note:'' one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click ''Save query''. This will build the query string for you. All you need to do is remove the extra line breaks. 34 35 ''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. 36 34 37 35 38 === Using TracLinks === … … 65 68 [[TicketQuery(version=0.6|0.7&resolution=duplicate)]] 66 69 67 Just like the [wiki:TracQuery#UsingTracLinks query: wiki links], the parameter of this macro expects a query string formatted according to the rules of the simple [wiki:TracQuery#QueryLanguage ticket query language]. 70 Just like the [wiki:TracQuery#UsingTracLinks query: wiki links], the parameter of this macro expects a query string formatted according to the rules of the simple [wiki:TracQuery#QueryLanguage ticket query language]. This also allows displaying the link and description of a single ticket: 71 {{{ 72 [[TicketQuery(id=123)]] 73 }}} 74 75 This is displayed as: 76 [[TicketQuery(id=123)]] 68 77 69 78 A more compact representation without the ticket summaries is also available: … … 75 84 [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]] 76 85 77 Finally if you wish to receive only the number of defects that match the query usingthe ``count`` parameter.86 Finally, if you wish to receive only the number of defects that match the query, use the ``count`` parameter. 78 87 79 88 {{{ … … 107 116 === Query Language === 108 117 109 `query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Basically, the filters are separated by ampersands (`&`). Each filter then consists of the ticket field name, an operator, and one or more values. More than one value are separated by a pipe (`|`), meaning that the filter matches any of the values. To include a lit teral `&` or `|` in a value, escape the character with a backslash (`\`).118 `query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Basically, the filters are separated by ampersands (`&`). Each filter then consists of the ticket field name, an operator, and one or more values. More than one value are separated by a pipe (`|`), meaning that the filter matches any of the values. To include a literal `&` or `|` in a value, escape the character with a backslash (`\`). 110 119 111 120 The available operators are: 112 || '''`=`''' || the field content exactly matches theone of the values ||121 || '''`=`''' || the field content exactly matches one of the values || 113 122 || '''`~=`''' || the field content contains one or more of the values || 114 123 || '''`^=`''' || the field content starts with one of the values ||