| 11 | | 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. |
| | 10 | When you first go to the query page, the default filter will display tickets relevant to you: |
| | 11 | * If logged in, all open tickets assigned to you. |
| | 12 | * If not logged in, but you have specified a name or email address in the preferences, all open tickets where your name or email is in the CC list. |
| | 13 | * If not logged in and no name/email is defined in the preferences, then all open issues. |
| 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 | Filters with either a text box or a dropdown menu of options can be added multiple times to perform an ''Or'' on the criteria. Add additional 'Or's by Clicking the 'And' Dropdown and selecting an item that you have already selected. For example, to select "Milestone is X ''Or'' Milestone is Y", Select 'Milestone', Select 'X', then click the 'And' Dropdown, select 'Milestone' a second time and select 'Y'. |
| | 20 | |
| | 21 | For text fields such as Keywords and CC the `-` operator can be used to negate a match and double quotes (//since 1.2.1//) can be used to match a phrase. For example, a //contains// match for `word1 word2 -word3 "word4 word5"` matches tickets containing `word1` and `word2`, not `word3` and `word4 word5`. |
| | 22 | |
| | 23 | You can use the controls just below the filters box to group the results based on a field, or display the full description for each ticket. |
| | 24 | |
| | 25 | Keyboard shortcuts are available for manipulating the //checkbox// filters: |
| | 26 | * Clicking on a filter row label toggles all checkboxes. |
| | 27 | * Pressing the modifier key while clicking on a filter row label inverts the state of all checkboxes. |
| | 28 | * Pressing the modifier key while clicking on a checkbox selects the checkbox and deselects all other checkboxes in the filter. Since 1.2.1 this also works for the //Columns// checkboxes. |
| | 29 | |
| | 30 | The modifier key is platform and browser dependent. On Mac the modified key is !Option/Alt or Command. On Linux the modifier key is Ctrl + Alt. Opera on Windows seems to use Ctrl + Alt, while Alt is effective for other Windows browsers. |
| | 31 | |
| | 32 | == Navigating Tickets |
| | 33 | |
| | 34 | Clicking on one of the query results will take you to that ticket. You can navigate through the results by clicking the ''Next Ticket'' or ''Previous Ticket'' links just below the main menu bar, or click the ''Back to Query'' link to return to the query page. |
| | 35 | |
| | 36 | 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 were 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. If '''a new ticket matching the query criteria has been created''', it will be shown in bold. |
| 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. |
| | 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 (`\`). |
| 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 || |
| | 72 | || '''`=`''' || the field content exactly matches one of the values || |
| | 73 | || '''`~=`''' || the field content contains one or more of the values || |
| | 74 | || '''`^=`''' || the field content starts with one of the values || |
| | 75 | || '''`$=`''' || the field content ends with one of the values || |
| 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 || |
| | 78 | || '''`!=`''' || the field content matches none of the values || |
| | 79 | || '''`!~=`''' || the field content does not contain any of the values || |
| | 80 | || '''`!^=`''' || the field content does not start with any of the values || |
| | 81 | || '''`!$=`''' || the field content does not end with any of the values || |
| | 82 | |
| | 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`. |
| | 84 | || '''`status=closed,keywords~=firefox`''' || query closed tickets that contain keyword `firefox` || |
| | 85 | || '''`status=closed,keywords~=opera`''' || query closed tickets that contain keyword `opera` || |
| | 86 | || '''`status=closed,keywords~=firefox opera`''' || query closed tickets that contain keywords `firefox` and `opera` || |
| | 87 | || '''`status=closed,keywords~=firefox|opera`''' || query closed tickets that contain keywords `firefox` or `opera` || |
| | 88 | || '''`status=closed,keywords~=firefox,or,keywords~=opera`''' || query closed tickets that contain keyword `firefox`, or (closed or unclosed) tickets that contain keyword `opera` || |
| | 89 | || '''`status=closed,keywords~=firefox -opera`''' || query closed tickets that contain keyword `firefox`, but not `opera` || |
| | 90 | || '''`status=closed,keywords~=opera -firefox`''' || query closed tickets that contain keyword `opera`, but no `firefox` || |
| | 91 | |
| | 92 | The date fields `created` and `modified` 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 || |
| | 94 | || '''`created=lastmonth..thismonth`''' || query tickets created during the previous month || |
| | 95 | || '''`modified=1weekago..`''' || query tickets that have been modified in the last week || |
| | 96 | || '''`modified=..30daysago`''' || query tickets that have been inactive for the last 30 days || |
| | 97 | |
| | 98 | Note that `modified` is the //last modified time//, so `modified` with a date range shows ticket that were //last modified// in that date range. If a ticket was modified in the date range, but modified again after the end date, it will not be included in the results. |
