| Version 2 (modified by , 15 years ago) ( diff ) |
|---|
Trac Ticket Queries
Table of Contents
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.
Navigating Tickets
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.
Using TracLinks
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:
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:
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:
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 5337)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5821 | fixed | PG18 crashing on master branch (3.6) on tickets regress | ||
| #5815 | fixed | hash operator error | ||
| #5812 | fixed | ST_Within performance regression |
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 5337)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5821 | fixed | PG18 crashing on master branch (3.6) on tickets regress | ||
| Description |
I was seeing reds on Debbie and Github, but woodie is fine. On further inspection these appear to only be in PG18. debbie https://debbie.postgis.net/job/PostGIS_Regress/32179/consoleFull 16:25:03 psql:tickets.sql:1019: NOTICE: Hole lies outside shell at or near point 25495368.044100001 6671726.9312000005 16:25:03 #3719a|f 16:25:03 #3719b|t 16:25:03 #3774|t 16:25:03 #1014a|POINT(0 0) 16:25:03 #1014a|POINT(0 0) 16:25:03 #1014b|POINT(0 1) 16:25:03 psql:tickets.sql:1047: server closed the connection unexpectedly 16:25:03 This probably means the server terminated abnormally 16:25:03 before or while processing the request. 16:25:03 psql:tickets.sql:1047: error: connection to server was lost 16:25:03 ------------------------------------------------------------ github https://github.com/postgis/postgis/actions/runs/12323216874/job/34398402435 psql:tickets.sql:1019: NOTICE: Hole lies outside shell at or near point 25495368.044100001 6671726.9312000005 #3719a|f #3719b|t #3774|t #1014a|POINT(0 0) #1014a|POINT(0 0) #1014b|POINT(0 1) psql:tickets.sql:1047: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. psql:tickets.sql:1047: error: connection to server was lost So they are failing on same place in 1047 which has this query SELECT '#1014c', id, st_astext(g) FROM path; |
|||
| #5815 | fixed | hash operator error | ||
| Description |
On IRC velix mentioned this bug in PostGIS 3.5.0. I haven't tested prior versions but I suspect is a regression. To generate the error: WITH lines AS (SELECT ST_GeomFromText('LINESTRING(1 2, 3 4)') AS geom
UNION ALL
SELECT ST_GeomFromText('LINESTRING(6 5, 7 8)') AS geom
)
SELECT t1.geom, t2.geom
FROM lines AS t1, lines AS t2
WHERE t1.geom <> t2.geom;
Error is - I think hash operator id might change ERROR: could not find hash function for hash operator 1192459 |
|||
| #5812 | fixed | ST_Within performance regression | ||
| Description |
ST_Within is far slower than the equivalent ST_Contains, due to a mistake in the prepgeom caching handling. |
|||
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
