16 | | You can edit the query by clicking ''Refine Query''. |
| 18 | You can safely edit any of the tickets and continue to navigate through the results using the ''Next/Previous/Back to Query'' links after saving your results. When you return to the query ''any tickets which was edited'' will be displayed with italicized text. If one of the tickets was edited such that [[html(<span style="color: grey">it no longer matches the query criteria </span>)]] the text will also be greyed. Lastly, if '''a new ticket matching the query criteria has been created''', it will be shown in bold. |
| 19 | |
| 20 | The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again. |
| 21 | |
| 22 | == Saving Queries == |
| 23 | |
| 24 | While Trac does not yet allow saving a named query and somehow making it available in a navigable list, you can save references to queries in Wiki content, as described below. |
| 25 | |
| 26 | === Using TracLinks === |
| 27 | |
| 28 | You may want to save some queries so that you can come back to them later. You can do this by making a link to the query from any Wiki page. |
| 29 | {{{ |
| 30 | [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0] |
| 31 | |
| 32 | }}} |
| 33 | |
| 34 | Which is displayed as: |
| 35 | [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0] |
| 36 | |
| 37 | This uses a very simple query language to specify the criteria (see [wiki:TracQuery#QueryLanguage Query Language]). |
| 38 | |
| 39 | Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading `?` character: |
| 40 | {{{ |
| 41 | [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner] |
| 42 | |
| 43 | }}} |
| 44 | |
| 45 | Which is displayed as: |
| 46 | [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner] |
| 47 | |
| 48 | === Using the `[[TicketQuery]]` Macro === |
| 49 | |
| 50 | The TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting. |
| 51 | |
| 52 | Example: |
| 53 | {{{ |
| 54 | [[TicketQuery(version=0.6|0.7&resolution=duplicate)]] |
| 55 | }}} |
| 56 | |
| 57 | This is displayed as: |
| 58 | [[TicketQuery(version=0.6|0.7&resolution=duplicate)]] |
| 59 | |
| 60 | 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]. |
| 61 | |
| 62 | A more compact representation without the ticket summaries is also available: |
| 63 | {{{ |
| 64 | [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]] |
| 65 | |
| 66 | }}} |
| 67 | |
| 68 | This is displayed as: |
| 69 | [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]] |
| 70 | |
| 71 | Finally if you wish to receive only the number of defects that match the query using the ``count`` parameter. |
| 72 | |
| 73 | {{{ |
| 74 | [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]] |
| 75 | |
| 76 | }}} |
| 77 | |
| 78 | This is displayed as: |
| 79 | [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]] |
| 80 | |
| 81 | |
| 82 | === Query Language === |
| 83 | |
| 84 | `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. |
| 85 | |
| 86 | The available operators are: |
| 87 | || '''=''' || the field content exactly matches the one of the values || |
| 88 | || '''~=''' || the field content contains one or more of the values || |
| 89 | || '''!^=''' || the field content starts with one of the values || |
| 90 | || '''$=''' || the field content ends with one of the values || |
| 91 | |
| 92 | All of these operators can also be negated: |
| 93 | || '''!=''' || the field content matches none of the values || |
| 94 | || '''!~=''' || the field content does not contain any of the values || |
| 95 | || '''!!^=''' || the field content does not start with any of the values || |
| 96 | || '''!$=''' || the field content does not end with any of the values || |