wiki:TicketQuery

Version 4 (modified by trac, 7 months 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: 1 [[TicketQuery(status=new&milestone=,count)]]
Number of new tickets: 1 [[TicketQuery(status=new,count)]]
Number of reopened tickets: 0 [[TicketQuery(status=reopened,count)]]
Number of assigned tickets: 0 [[TicketQuery(status=assigned,count)]]
Number of invalid tickets: 7 [[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets: 11 [[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets: 1 [[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets: 7 [[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets: 80 [[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset): 4 [[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets: 110 [[TicketQuery(count)]]
Number of tickets reported or owned by current user: 7 [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
Number of tickets created this month: 1 [[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: #180, #179, #122 [[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 weber weber
Summary Error message "Wrong observation epoch(s)"

Format: list

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

This is displayed as:

No results

[[TicketQuery(id=123)]]

This is displayed as:

#123
BKG caster does not actively close server connections

Format: compact

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

This is displayed as:

No results

Format: count

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

This is displayed as:

0

Format: progress

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

This is displayed as:

defect

79 / 82

enhancement

15 / 16

task

12 / 12

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 in 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 106)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#180 fixed accidentaly uploaded a sourcetable.dat file team ahmed.sobhy@…
#179 fixed reload config on demand stuerze wiese
#176 fixed Ephemeris state not check based on current time in real-time processing stuerze lucia
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 106)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#180 fixed accidentaly uploaded a sourcetable.dat file team ahmed.sobhy@…
Description

I would like to delete the sourcetable.dat attachment I uploaded please.

#179 fixed reload config on demand stuerze wiese
Description

currently you can configure that BNC reloads its configuration in certain time intervals, e.g. once per day. See 'General > Reread configuration'.

But often it's necassary to reload at once after a change in the config. A restart would disconnect all connections and jobs, what is mostly not wanted.

It's usual to send a SIGHUP to the process, you want to reload. From systemd: "...reload will reload a specific service. That means that the systemd will send a SIGHUP signal to a service, and that signal will tell the service to reload its configuration file."

#176 fixed Ephemeris state not check based on current time in real-time processing stuerze lucia
Description

In PPP processing, the satellite position is obtained from the applicable navigation message. There is a check on whether this message can be used or whether it should be discarded because it is unhealthy, outdated or bad-formed. However, from the current implementation, it seems that in real-time processing this status is only defined at the time the message arrives for the first time. Therefore, if a navigation message is not updated, exceeding the validity time, but the satellite is still in view, the outdated navigation message may be used.

I think that in real-time inside the PPP processing, when the getCrd function is called, it is necessary to relaunch the checkEphemeris to ensure the ephemeris saved in the database is still valid and not outdated.

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.