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: 28 [[TicketQuery(status=new&milestone=,count)]]
Number of new tickets: 67 [[TicketQuery(status=new,count)]]
Number of reopened tickets: 3 [[TicketQuery(status=reopened,count)]]
Number of assigned tickets: 42 [[TicketQuery(status=assigned,count)]]
Number of invalid tickets: 23 [[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets: 11 [[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets: 18 [[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets: 28 [[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets: 447 [[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset): 35 [[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets: 816 [[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: #215, #811, #568 [[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 Olly Betts Olly Betts
Summary Put Xapian in a namespace

Format: list

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

This is displayed as:

No results

[[TicketQuery(id=123)]]

This is displayed as:

#123
Adding large documents to remote db may cause a timeout

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:

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#819 fixed What is the impact of block_size parameter in Database::compact method ? Olly Betts mgautier
#818 invalid Build issue with 1.14.4 under python 3.12 Richard Boulton rouilj
#816 fixed expand/ortermlist.cc:166:12: warning: duplicated 'if' condition Olly Betts dcb
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 704)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#819 fixed What is the impact of block_size parameter in Database::compact method ? Olly Betts mgautier
Description

It is unclear to me how the block_size parameter will impact the database.

For a bit of context, we are indexing content once, compact the database (with Compactor::FULLER flag) and distribute the database (readonly) on which we search.

What would be the impact the the block_size ? Does it have a impact on the database size, on searching performance, both ?

It may be good to add this information to the documentation (this way my ticket is really an enhancement and not a simple question :) )

Thanks

#818 invalid Build issue with 1.14.4 under python 3.12 Richard Boulton rouilj
Description

I am trying to compile 1.4.14 bindings for use with python 3.12 in my CI/CD pipeline for the Roundup Issue Tracker. We use xapian for one of our full text search implementations.

In addition to some deprecation warnings (that I think also occur when building under Python 3.11), we get syntax errors of the form:

In file included from /opt/python/3.12-dev/include/python3.12/Python.h:45,
                 from xapian_wrap.cc:22:
xapian_wrap.cc: In function ‘PyObject* SwigPyObject_New(void*, swig_type_info*, int)’:
/opt/python/3.12-dev/include/python3.12/objimpl.h:134:45: error: expected primary-expression before ‘)’ token
  134 | #define PyObject_New(type, typeobj) ((type *)_PyObject_New(typeobj))
      |                                             ^
/opt/python/3.12-dev/include/python3.12/objimpl.h:138:37: note: in expansion of macro ‘PyObject_New’
  138 | #define PyObject_NEW(type, typeobj) PyObject_New((type), (typeobj))
      |                                     ^~~~~~~~~~~~
xapian_wrap.cc:2148:24: note: in expansion of macro ‘PyObject_NEW’
 2148 |   SwigPyObject *sobj = PyObject_NEW(SwigPyObject, SwigPyObject_type());
      |                        ^~~~~~~~~~~~
/opt/python/3.12-dev/include/python3.12/objimpl.h:134:46: error: expected ‘)’ before ‘_PyObject_New’
  134 | #define PyObject_New(type, typeobj) ((type *)_PyObject_New(typeobj))
      |                                     ~        ^~~~~~~~~~~~~
/opt/python/3.12-dev/include/python3.12/objimpl.h:138:37: note: in expansion of macro ‘PyObject_New’
  138 | #define PyObject_NEW(type, typeobj) PyObject_New((type), (typeobj))
      |                                     ^~~~~~~~~~~~
xapian_wrap.cc:2148:24: note: in expansion of macro ‘PyObject_NEW’
 2148 |   SwigPyObject *sobj = PyObject_NEW(SwigPyObject, SwigPyObject_type());
      |                        ^~~~~~~~~~~~

The full log is visible at: https://app.travis-ci.com/github/roundup-tracker/roundup/jobs/574465489#L980. Before that line are the deprecations.

Is this build supposed to work the same as for Python 3.10, 3.11?

Thanks.

-- rouilj

#816 fixed expand/ortermlist.cc:166:12: warning: duplicated 'if' condition Olly Betts dcb
Description

gcc with compiler flag -Wduplicated-cond says

xpand/ortermlist.cc:166:12: warning: duplicated 'if' condition [-Wduplicated-cond]

166 | } else if (cmp < 0) {

| ~

expand/ortermlist.cc:158:5: note: previously used here

158 | if (cmp < 0) {

| ~

1 2 3 4 5 6 7 8 9 10 11


See also: TracQuery, TracTickets, TracReports

Last modified 3 years ago Last modified on 24/11/19 00:43:22
Note: See TracWiki for help on using the wiki.