wiki:TicketQuery

TicketQuery Wiki Macro

The TicketQuery macro lets you display ticket information anywhere that accepts WikiFormatting. The query language used by the [[TicketQuery]] macro is described in the TracQuery page.

Usage

[[TicketQuery]]

Wiki macro listing tickets that match certain criteria.

This macro accepts a comma-separated list of keyed parameters, in the form "key=value".

If the key is the name of a field, the value must use the syntax of a filter specifier as defined in TracQuery#QueryLanguage. Note that this is not the same as the simplified URL syntax used for query: links starting with a ? character. Commas (,) can be included in field values by escaping them with a backslash (\).

Groups of field constraints to be OR-ed together can be separated by a literal or argument.

In addition to filters, several other named parameters can be used to control how the results are presented. All of them are optional.

The format parameter determines how the list of tickets is presented:

  • list -- the default presentation is to list the ticket ID next to the summary, with each ticket on a separate line.
  • compact -- the tickets are presented as a comma-separated list of ticket IDs.
  • count -- only the count of matching tickets is displayed
  • rawcount -- only the count of matching tickets is displayed, not even with a link to the corresponding query (since 1.1.1)
  • table -- a view similar to the custom query view (but without the controls)
  • progress -- a view similar to the milestone progress bars

The max parameter can be used to limit the number of tickets shown (defaults to 0, i.e. no maximum).

The order parameter sets the field used for ordering tickets (defaults to id).

The desc parameter indicates whether the order of the tickets should be reversed (defaults to false).

The group parameter sets the field used for grouping tickets (defaults to not being set).

The groupdesc parameter indicates whether the natural display order of the groups should be reversed (defaults to false).

The verbose parameter can be set to a true value in order to get the description for the listed tickets. For table format only. deprecated in favor of the rows parameter

The rows parameter can be used to specify which field(s) should be viewed as a row, e.g. rows=description|summary

The col parameter can be used to specify which fields should be viewed as columns. For table format only.

For compatibility with Trac 0.10, if there's a last positional parameter given to the macro, it will be used to specify the format. Also, using "&" as a field separator still works (except for order) but is deprecated.

Examples

Example Result Macro
Number of Triage tickets: 19 [[TicketQuery(status=new&milestone=,count)]]
Number of new tickets: 19 [[TicketQuery(status=new,count)]]
Number of reopened tickets: 1 [[TicketQuery(status=reopened,count)]]
Number of assigned tickets: 0 [[TicketQuery(status=assigned,count)]]
Number of invalid tickets: 15 [[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets: 6 [[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets: 6 [[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets: 49 [[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets: 247 [[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset): 21 [[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets: 344 [[TicketQuery(count)]]
Number of tickets reported or owned by current user: 0 [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
Number of tickets created this month: 0 [[TicketQuery(created=thismonth..,count)]]
Number of closed Firefox tickets: 0 [[TicketQuery(status=closed,keywords~=firefox,count)]]
Number of closed Opera tickets: 0 [[TicketQuery(status=closed,keywords~=opera,count)]]
Number of closed tickets affecting Firefox and Opera: 0 [[TicketQuery(status=closed,keywords~=firefox opera,count)]]
Number of closed tickets affecting Firefox or Opera: 0 [[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
Number of tickets that affect Firefox or are closed and affect Opera: 0 [[TicketQuery(status=closed,keywords~=opera,or,keywords~=firefox,count)]]
Number of closed Firefox tickets that don't affect Opera: 0 [[TicketQuery(status=closed,keywords~=firefox -opera,count)]]
Last 3 modified tickets: #338, #344, #343 [[TicketQuery(max=3,order=modified,desc=1,compact)]]

Details of ticket #1:

[[TicketQuery(id=1,col=id|owner|reporter,rows=summary,table)]]

Ticket Owner Reporter
#1 Felix Kästner
Summary Trac Email verification url points to htts instead of https

Format: list

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

This is displayed as:

#36
Backup vor Systemupgrade
#148
IPv6-Adresse für Router
#211
trac: Generierte Paßwörter führen zu Traceback
#228
Nextcloud auf einem Server im Space installieren
#244
Munin processing time liefert keine Zahlen
#337
raw.git.kraut.space einrichten

[[TicketQuery(id=123)]]

This is displayed as:

#123
Serverwahl als weisskraut-Ersatz

Format: compact

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

This is displayed as:

#36, #148, #211, #228, #244, #337

Format: count

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

This is displayed as:

6

Format: progress

[[TicketQuery(milestone=0.12.8&group=type,format=progress)]]

This is displayed as:

defect

100 / 103

enhancement

88 / 98

task

135 / 143

Format: table

You can choose the columns displayed in the table format (format=table) using col=<field>. You can specify multiple fields and the order they are displayed by placing pipes (|) between the columns:

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

This is displayed as:

Results (1 - 3 of 323)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#344 fixed Kontakt in Kommunikation umbenennen berhsi Jens Kubieziel
#343 fixed Discourse in die Webseite aufnehmen? berhsi Jens Kubieziel
#339 fixed Der NextCloud eine Gruppe alle hinzufügen und die Accounts eintragen Jens Kubieziel Jens Kubieziel
1 2 3 4 5 6 7 8 9 10 11

Full rows

In table format you can specify full rows using rows=<field>:

[[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 323)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#344 fixed Kontakt in Kommunikation umbenennen berhsi Jens Kubieziel
Description

Auf der rechten Seite der Webseite steht aktuell "Kontakt". Aus meiner Sicht passt "Kommunikation" besser. Wenn man das so umsetzt, wäre es sinnvoll, den Link zur ICS-Datei rauszunehmen. Das ist weder eine Kontaktmöglichkeit noch Kommunikation.

Es bietet sich vielleicht an, die ICS-Datei unterhalb der Termine zum Download anzubieten.

Wie findest du den Vorschlag?

#343 fixed Discourse in die Webseite aufnehmen? berhsi Jens Kubieziel
Description

Wir haben jetzt das Discourse als Kommunikationsplattform. Eventuell wäre das sinnvoll, dies auch auf die Webseite zu schreiben.

Bernd, was meinst du dazu? Wo könnte man das eventuell unterbringen?

#339 fixed Der NextCloud eine Gruppe alle hinzufügen und die Accounts eintragen Jens Kubieziel Jens Kubieziel
Description

l.behm hat in der Matrix angeregt, eine Gruppe namens alle einzurichten und dort die Accounts einzutragen. Mitglieder der Gruppe könnten einen gemeinsamen Kalender pflegen, der Termine des Hackspace' enthält.

  • Gruppe anlegen
  • Account dort zuordnen
1 2 3 4 5 6 7 8 9 10 11


See also: TracQuery, TracTickets, TracReports

Last modified 10 months ago Last modified on Oct 22, 2021, 8:34:04 PM
Note: See TracWiki for help on using the wiki.