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: | 6 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 11 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 1 | [[TicketQuery(status=reopened,count)]]
|
| Number of assigned tickets: | 2 | [[TicketQuery(status=assigned,count)]]
|
| Number of invalid tickets: | 5 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 5 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 2 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 11 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 81 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 6 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 118 | [[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: | #75, #45, #59 | [[TicketQuery(max=3,order=modified,desc=1,compact)]]
|
Details of ticket #1: |
| |
| ||
Format: list
[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
This is displayed as:
No results
[[TicketQuery(id=123)]]
This is displayed as:
No results
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:
Format: progress
[[TicketQuery(milestone=0.12.8&group=type,format=progress)]]
This is displayed as:
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 104)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #117 | fixed | atlod rfiflag L/S range needs to be updated | ||
| #116 | invalid | gpnorm failing when bandpass tables are present | ||
| #115 | fixed | gpcal not calibrating correctly |
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 104)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #117 | fixed | atlod rfiflag L/S range needs to be updated | ||
| Description |
With 4 out of the 5 L/S receivers currently on the array being the wideband type, it is time to update atlod to stop it cutting out too much of the usable band. Currently, when 'options=birdie,rfiflag' is specified to atlod while loading L data, the band outside the range 1.2 - 1.9 GHz is flagged. I propose that the full 1.1 - 3.1 GHz range be made available. This will probably have to be date-dependent, to support old CABB data. I think all L/S data after 17th August 2010 can be assumed to have the entire L/S range usable for antennas 2,3,4 and 6. At this time, CA01 still has the old L/S band receiver, and antennas 1 & 5 will be upgraded by 22nd October 2010. |
|||
| #116 | invalid | gpnorm failing when bandpass tables are present | ||
| Description |
For reference please see conversation at http://atcaforum.freeforums.org/gpnorm-gives-fatal-error-when-bandpass-tables-are-present-t39.html Dominic reports that the gpnorm task does not work on a dataset that has a bandpass table or correction applied. He further states that this is a recent issue and that previous gpnorm versions did not suffer from this. |
|||
| #115 | fixed | gpcal not calibrating correctly | ||
| Description |
For reference please see conversation at: http://atcaforum.freeforums.org/l-band-flux-of-1934-638-depends-on-maxsize-t38.html It appears that when a heavily flagged (in frequency space) 1934-638 dataset is input into gpcal, the resultant flux appears to be incorrect. Is gpcal merely scaling the entire band to make the average flux level match the flux level expected of 1934-638 at the "centre" of the band? Is this a problem for other sources? The mfcal task does not suffer from this defect. Some example data that I used to replicate this problem can be found at /DATA/KAPUTAR_3/ste616/reduction/dominic_problem/. Here, the 1934-638.1750.1 dataset can be calibrated using mfcal/gpcal to see how the flux levels vary between the two calibration methods (the spectral slope appears to stay the same). The dataset 1934-638.1750.aver removes the large flagged areas on either side of the usable part of the spectrum, and calibrating with this dataset results in a much smaller difference. With this result, it would seem that gpcal has always been giving faulty results, although in the higher frequency bands where less spectral flagging is required, the effect is too small to be noticed. |
|||
See also: TracQuery, TracTickets, TracReports
