Version 1 (modified by trac, 4 years ago)

--

Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, used to display lists of tickets meeting a specified set of criteria.

To configure and execute a custom query, switch to the View Tickets module from the navigation bar, and select the Custom Query link.

Filters

When you first go to the query page the default filters will display all open tickets, or if you're logged in it will display open tickets assigned to you. 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 list in the bottom-right corner of the filters box. Filters with either a text box or a pulldown menu of options can be added multiple times to perform an or of the criteria.

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.

Once you've edited your filters click the Update button to refresh your results.

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.

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 it no longer matches the query criteria the text will also be greyed. Lastly, if a new ticket matching the query criteria has been created, it will be shown in bold.

The query results can be refreshed and cleared of these status indicators by clicking the Update button again.

Saving Queries

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.

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.

[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]

Which is displayed as:

Active tickets against 1.0

This uses a very simple query language to specify the criteria (see Query Language).

Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading ? character:

[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]

Which is displayed as:

Assigned tickets by owner

Using the [[TicketQuery]] Macro

The  TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.

Example:

[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]

This is displayed as:

No results

Just like the query: wiki links, the parameter of this macro expects a query string formatted according to the rules of the simple ticket query language.

A more compact representation without the ticket summaries is also available:

[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]

This is displayed as:

No results

Finally if you wish to receive only the number of defects that match the query using the count parameter.

[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]

This is displayed as:

0

Customizing the table format

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:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Results (1 - 3 of 22)

Ticket Resolution Summary Owner Reporter
#27 fixed Test ticket for ticket show details eelco@… eelco@…
#25 fixed As of april 21st, around 16:00 about 5 code revisions have been lost david.vanenckevort@… work@…
#22 fixed Project admin page editable by logged in user, not just admins support@… tim.te.beek@…

Full rows

In table format you can also have full rows by using rows=<field> like below:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]

This is displayed as:

Results (1 - 3 of 22)

Ticket Resolution Summary Owner Reporter
#27 fixed Test ticket for ticket show details eelco@… eelco@…

Reported by eelco@…, 2 years ago.

description

This is a test ticket to see changes to ticket_show_details option in trac.ini

#25 fixed As of april 21st, around 16:00 about 5 code revisions have been lost david.vanenckevort@… work@…

Reported by work@…, 3 years ago.

description

This afternoon we noticed our contiuous integration build was not updating properly after code commits, and more interestingly the continuous integration build was running revision 1790 ( http://ci.nmcdsp.org) while the latest commit today was revision 1786 ( https://trac.nbic.nl/gscf/log/trunk).

As I know SVN + TRAC was migrated last week I assume that somehow a SVN state has been migrated which is lacking the last 5 commits: quote

Dear all,

Please note that the Trac server https://trac.nbic.nl/ will be
migrated to a different compute center Thursday morning 21/4. This
will result in a temporary service disruption.

More details later.

Rob

-- 
Rob W.W. Hooft
Chief Technology Officer BioAssist, Netherlands Bioinformatics Centre

From our continuous integration build log we see the continuous integration works fine until 16:00

201104211445 newer version of gscf is available
201104211445 deploying revision 1788 (version 0.8.0 / Grails 1.3.7) and undeploying revision 1787...
201104211445 uninstalling webtest plugin
201104211445 uninstalling db-util plugin
201104211445 uninstalling grom plugin
201104211445 setting build information variables in application.properties
201104211445 current workdirectory: /home/tomcat/workspace/gscf
201104211445 building new ci war...
201104211446 project deployment is still happening
201104211445 stopping gscf-0.8.0-ci
201104211445 undeploying gscf-0.8.0-ci
201104211445 deploying new ci WAR
201104211445 updating apache virtual host configuration
201104211445 reloading Apache
201104211445 done deploying gscf revision 1788 (version 0.8.0)
201104211459 newer version of gscf is available
201104211459 deploying revision 1789 (version 0.8.0 / Grails 1.3.7) and undeploying revision 1788...
201104211459 setting build information variables in application.properties
201104211459 current workdirectory: /home/tomcat/workspace/gscf
201104211459 building new ci war...
201104211500 project deployment is still happening
201104211459 stopping gscf-0.8.0-ci
201104211459 undeploying gscf-0.8.0-ci
201104211459 deploying new ci WAR
201104211459 updating apache virtual host configuration
201104211459 reloading Apache
201104211459 done deploying gscf revision 1789 (version 0.8.0)
201104211550 newer version of gscf is available
201104211550 deploying revision 1790 (version 0.8.0 / Grails 1.3.7) and undeploying revision 1789...
201104211550 uninstalling webtest plugin
201104211550 uninstalling db-util plugin
201104211550 uninstalling grom plugin
201104211550 setting build information variables in application.properties
201104211550 current workdirectory: /home/tomcat/workspace/gscf
201104211550 building new ci war...
201104211551 project deployment is still happening
201104211550 stopping gscf-0.8.0-ci
201104211550 undeploying gscf-0.8.0-ci
201104211550 deploying new ci WAR
201104211550 updating apache virtual host configuration
201104211550 reloading Apache
201104211550 done deploying gscf revision 1790 (version 0.8.0)

after which the svn state was broken:

svn: No such revision 1790
201104211619 haven't got an svn revision?
svn: No such revision 1790
svn: No such revision 1790
201104211620 haven't got an svn revision?

I don't know what happened, but we: 1. are missing 5 code revisions 2. have a conflict as code has now been committed as revision #1786 which should have been #1791

I'm sure you are aware of the seriousness of this issue, so I hope this can be resolved ASAP

#22 fixed Project admin page editable by logged in user, not just admins support@… tim.te.beek@…

Reported by tim.te.beek@…, 3 years ago.

description

Any logged in user can administrate any project, by altering the below URL in a predictable manner:  https://trac.nbic.nl/admin/ProjectAdmin.php?mode=editproject&project=sandbox

Currently the only requirement is that the user is logged in, not whether or not the user is an administrator for the project. This constitutes a mayor security project for every current Trac project.

Query Language

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.

The available operators are:

= the field content exactly matches the one of the values
~= the field content contains one or more of the values
^= the field content starts with one of the values
$= the field content ends with one of the values

All of these operators can also be negated:

!= the field content matches none of the values
!~= the field content does not contain any of the values
!^= the field content does not start with any of the values
!$= the field content does not end with any of the values

See also: TracTickets, TracReports, TracGuide