Edgewall Software

Changes between Version 31 and Version 60 of TracQuery


Ignore:
Timestamp:
(multiple changes)
Author:
(multiple changes)
Comment:
(multiple changes)

Legend:

Unmodified
Added
Removed
Modified
  • TracQuery

    v31 v60  
    1 ** Note: this page documents the 0.12 version of Trac, see [[0.11/TracQuery]] if you need the previous version **
    2 = Trac Ticket Queries =
     1= Trac Ticket Queries
    32[[TracGuideToc]]
    43[[TranslatedPages]]
    54
    6 In addition to [wiki:TracReports reports], Trac provides support for ''custom ticket queries'', used to display lists of tickets meeting a specified set of criteria.
     5In addition to [TracReports reports], Trac provides ''custom ticket queries'', which display tickets meeting specified criteria.
    76
    8 To configure and execute a custom query, switch to the ''View Tickets'' module from the navigation bar, and select the ''Custom Query'' link.
     7To configure and execute a custom query, navigate to the ''View Tickets'' module from the navigation bar, and select the ''New Custom Query'' link.
    98
    10 == Filters ==
     9== Filters
    1110
    12 When you first go to the query page the default filter will display tickets relevant to you:
    13  * If logged in then all open tickets it will display open tickets assigned to you.
    14  * If not logged in but you have specified a name or email address in the preferences then it will display all open tickets where your email (or name if email not defined) is in the CC list.
    15  * If not logged and no name/email defined in the preferences then all open issues are displayed.
     11When you first go to the query page, the default filter will display tickets relevant to you:
     12 * If logged in, all open tickets assigned to you.
     13 * 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.
     14 * If not logged in and no name/email is defined in the preferences, then all open issues.
    1615
    17 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.
     16New filters are added using the dropdown lists at the bottom corners of the filters box; 'And' conditions on the left, 'Or' conditions on the right. Filters are removed by clicking the button to the left with the minus sign on the label.
    1817
    19 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.
     18After you have edited your filters, click the ''Update'' button to refresh your results.
    2019
    21 Once you've edited your filters click the ''Update'' button to refresh your results.
     20Filters 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'.
    2221
    23 == Navigating Tickets ==
    24 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. 
     22For 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`.
    2523
    26 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. Lastly, if '''a new ticket matching the query criteria has been created''', it will be shown in bold.
     24You 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.
     25
     26Keyboard shortcuts are available for manipulating the //checkbox// filters:
     27* Clicking on a filter row label toggles all checkboxes.
     28* Pressing the modifier key while clicking on a filter row label inverts the state of all checkboxes.
     29* 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.
     30
     31The 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.
     32
     33== Navigating Tickets
     34
     35Clicking 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.
     36
     37You 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.
    2738
    2839The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again.
    2940
    30 == Saving Queries ==
     41== Saving Queries
    3142
    3243Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have ''Updated'' the view and then click the ''Save query'' button displayed beneath the results.
    3344You can also save references to queries in Wiki content, as described below.
    3445
    35 ''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.
     46'''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.
    3647
    37 === Using TracLinks ===
     48'''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.
    3849
    39 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.
     50== TracLinks to Queries
     51
     52You can make a link to a query from any Wiki page using a simple [TracQuery#QueryLanguage query language] to specify the criteria.
    4053{{{
    4154[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
     
    4558  [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
    4659
    47 This uses a very simple query language to specify the criteria (see [wiki:TracQuery#QueryLanguage Query Language]).
    48 
    49 Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading `?` character:
     60Alternatively, you can copy the query string from the browser URL box and paste it into the Wiki link, including the leading `?` character:
    5061{{{
    5162[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
     
    5566  [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
    5667
    57 === Using the `[[TicketQuery]]` Macro ===
     68== Query Language
    5869
    59 The [trac:TicketQuery TicketQuery] macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.
    60 
    61 Example:
    62 {{{
    63 [[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
    64 }}}
    65 
    66 This is displayed as:
    67   [[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
    68 
    69 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 
    71 A more compact representation without the ticket summaries is also available:
    72 {{{
    73 [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
    74 }}}
    75 
    76 This is displayed as:
    77   [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
    78 
    79 Finally, if you wish to receive only the number of defects that match the query, use the ``count`` parameter.
    80 
    81 {{{
    82 [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
    83 }}}
    84 
    85 This is displayed as:
    86   [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
    87 
    88 === Customizing the ''table'' format ===
    89 You can also customize the columns displayed in the table format (''format=table'') by using ''col=<field>'' - you can specify multiple fields and what order they are displayed by placing pipes (`|`) between the columns like below:
    90 
    91 {{{
    92 [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]
    93 }}}
    94 
    95 This is displayed as:
    96 [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]
    97 
    98 ==== Full rows ====
    99 In ''table'' format you can also have full rows by using ''rows=<field>'' like below:
    100 
    101 {{{
    102 [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]
    103 }}}
    104 
    105 This is displayed as:
    106 [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]
    107 
    108 
    109 === Query Language ===
    110 
    111 `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 (`\`).
     70The `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 (`\`).
    11271
    11372The available operators are:
     
    12382|| '''`!$=`''' || the field content does not end with any of the values ||
    12483
    125 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 left out to avoid having to quote the query string.
     84Filters 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`.
     85|| '''`status=closed,keywords~=firefox`''' || query closed tickets that contain keyword `firefox` ||
     86|| '''`status=closed,keywords~=opera`''' || query closed tickets that contain keyword `opera` ||
     87|| '''`status=closed,keywords~=firefox opera`''' || query closed tickets that contain keywords `firefox` and `opera` ||
     88|| '''`status=closed,keywords~=firefox|opera`''' || query closed tickets that contain keywords `firefox` or `opera` ||
     89|| '''`status=closed,keywords~=firefox,or,keywords~=opera`''' || query closed tickets that contain keyword `firefox`, or (closed or unclosed) tickets that contain keyword `opera` ||
     90|| '''`status=closed,keywords~=firefox -opera`''' || query closed tickets that contain keyword `firefox`, but not `opera` ||
     91|| '''`status=closed,keywords~=opera -firefox`''' || query closed tickets that contain keyword `opera`, but no `firefox` ||
     92
     93The 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.
    12694|| '''`created=2007-01-01..2008-01-01`''' || query tickets created in 2007 ||
    12795|| '''`created=lastmonth..thismonth`''' || query tickets created during the previous month ||
     
    12997|| '''`modified=..30daysago`''' || query tickets that have been inactive for the last 30 days ||
    13098
     99Note 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.
     100
    131101----
    132 See also: TracTickets, TracReports, TracGuide
     102See also: TracTickets, TracReports, TicketQuery