wiki:TicketQuery

Version 2 (modified by trac, 3 years ago) ( diff )

--

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: 116 [[TicketQuery(status=new&milestone=,count)]]
Number of new tickets: 116 [[TicketQuery(status=new,count)]]
Number of reopened tickets: 3 [[TicketQuery(status=reopened,count)]]
Number of assigned tickets: 7 [[TicketQuery(status=assigned,count)]]
Number of invalid tickets: 47 [[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets: 60 [[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets: 23 [[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets: 46 [[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets: 780 [[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset): 127 [[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets: 1083 [[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: #828, #245, #244 [[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 huub huub
Summary node down

Format: list

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

This is displayed as:

#12
AZC: Out of swap space
#13
AZC: Out of swap space
#113
syslogd start niet (meer) na reboot
#142
/var loopt vol
#165
dubbele b-flag voor syslogd
#241
Password sync svn/trac/wiki vanuit Drupal werkt niet meer
#309
Zwak signaal WBRotaryZW
#425
Node Kudelstaart uit de lucht
#451
HybridTUDelft-vr10 down
#529
HybridZTWMeerburgkerk-ue0 down
#746
HybridDrijfhuis - niet bereikbaar
#768
HybridWataertoren usb-lan adapter vervangen
#824
HybridKudelstaart VR10 niet bereikbaar
#825
HybridWatertoren3 UE0 down
#826
HybridZTWMeerburgkerk niet bereikbaar
#834
HybridZTWMeerburgkerk-ue0 Down volgens nagios
#850
HybridStadhuis-ue0 down volgens Nagios
#876
HybridAster Internet down
#962
ProxyWP.wleiden.net. down volgens Nagios
#982
HybridLHS nano vr2 geen response
#1010
HybridMeerburg usb adapters vervangen
#1028
HybridRoomburgh2 ue0 no buffer space
#1063
Meelfabriek geen stroom

[[TicketQuery(id=123)]]

This is displayed as:

#123
gformat does not properly write ip aliases file

Format: compact

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

This is displayed as:

#12, #13, #113, #142, #165, #241, #309, #425, #451, #529, #746, #768, #824, #825, #826, #834, #850, #876, #962, #982, #1010, #1028, #1063

Format: count

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

This is displayed as:

23

Format: progress

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

This is displayed as:

incident

751 / 804

problem

68 / 82

change

102 / 142

service request

34 / 54

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 956)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1082 invalid RT configuratie 'all dashboards' is leeg huub
#1081 invalid RT configuratie (Possible cross-site request forgery) huub
#1080 fixed JOP geen captive portal huub
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 956)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1082 invalid RT configuratie 'all dashboards' is leeg huub
Description

http://www.wirelessleiden.nl/support/Dashboards/index.html (waar je komt na kiezen van 'all dashboards') geeft een vrijwel leeg scherm.

#1081 invalid RT configuratie (Possible cross-site request forgery) huub
Description

Bij maken van nieuw ticket krijg ik de melding: Possible cross-site request forgery

RT has detected a possible cross-site request forgery for this request, because the Referrer header supplied by your browser (www.wirelessleiden.nl:80) is not allowed by RT's configured hostname (wirelessleiden.nl:443). A malicious attacker may be trying to create a ticket on your behalf. If you did not initiate this request, then you should alert your security team.

If you really intended to visit /support/Ticket/Create.html and create a ticket, then click here to resume your request.

#1080 fixed JOP geen captive portal huub
Description

Theo meldt dat signaalsterkte bij JOP uitstekend is, maar er is geen captive portal. Ik zie dat er nog een pf.hybrid.conf in /cfg stond uit de tijd dat dit de visitorcentre2 node was. Geinactiveerd, kijken of dat helpt.

1 2 3 4 5 6 7 8 9 10 11


See also: TracQuery, TracTickets, TracReports

Note: See TracWiki for help on using the wiki.