| Version 2 (modified by , 6 weeks 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: | 0 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 2 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 0 | [[TicketQuery(status=reopened,count)]]
|
| Number of assigned tickets: | 7 | [[TicketQuery(status=assigned,count)]]
|
| Number of invalid tickets: | 5 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 1 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 2 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 4 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 64 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 0 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 87 | [[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: | #85, #19, #84 | [[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 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 76)
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 76)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #87 | fixed | Cascading trap on exit | ||
| Description |
This happens randomly and not very frequently. Initial analysis from Steven which matches mine: Based on the .trp file I think this is the first dispatch of the exception handle:
DOS32R3EXCEPTIONDISPATCHER + 151 and _xcptR3ExceptionDispatcher - 23 and this is the return from the routine that trapped:
28D3 and ProcessConfigFile - 31D My build differs from yours, so you need to do the map using your .obj and ..map files. From the trap, the offset in the map to NewCommand_CurPos should be:
You need to verify this. The offset in the map to the address found on the stack is:
On my cfte.lst from wdis -l -s cfte.obj, I have
Adding the offset from the .trp file, we get
Searching for this offset in cfte.lst, I find:
and
which does not match exactly, but implies that the strncmp in PreprocessConfigFile call might have trapped. This is most likely:
If this is what triggered the trap, then cp.c is borked. Let me know what you find using your .map and wdis. FWIW, I'm somewhat expected there to be 2 trap reports in the .trp file, but this did not happen. Note the trp file and the dumps I have don't match up very well. I have 13 dump files from this event. |
|||
| #86 | fixed | Need to move mystrings.fte from the #2 warpin package to the #3 warpin pakage after the next release | ||
| #84 | fixed | Counter-intuitive double key press needed to input diacritic characters (instead of regular diacritic+space key combination) | ||
| Description |
Fixing ticket #79 introduced this one. In most languages other than English, some characters are overlaid on regular letters to form "combined" characters, f.e.: ¨ + o = ö through the use of "dead keys". Dead keys are not supposed to produce character output, this should happen only if a valid regular character is typed afterwards, and then a single combined character is produced. The fix for #79 drops all diacritic characters as typed, thus they can't be combined with a space to produce a standalone (non-diacritic) character when one is needed in the standard way all typists are used to. This defect is minor compared to #79, as the current PM implementation offers a simple yet counter-intuitive workaround: hitting a dead key twice will still type the standalone character, f.e. ^ + ^ = ^. Still, this should be fixed. Proposed fix: create a 1-char buffer to store diacritic characters as they are entered. The next time a space is typed, check for the right 'combined' flag, and output the last diacritic stored in the buffer instead. |
|||
See also: TracQuery, TracTickets, TracReports
