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: 438 [[TicketQuery(status=new&milestone=,count)]]
Number of new tickets: 438 [[TicketQuery(status=new,count)]]
Number of reopened tickets: 0 [[TicketQuery(status=reopened,count)]]
Number of assigned tickets: 652 [[TicketQuery(status=assigned,count)]]
Number of invalid tickets: 5319 [[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets: 1093 [[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets: 4445 [[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets: 4272 [[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets: 19360 [[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset): 1090 [[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets: 36609 [[TicketQuery(count)]]
Number of tickets reported or owned by current user: 1488 [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
Number of tickets created this month: 8 [[TicketQuery(created=thismonth..,count)]]
Number of closed Firefox tickets: 8 [[TicketQuery(status=closed,keywords~=firefox,count)]]
Number of closed Opera tickets: 26 [[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: 34 [[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
Number of tickets that affect Firefox or are closed and affect Opera: 34 [[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: #29291, #32577, #37396 [[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 Jacob Adrian Holovaty
Summary Create architecture for anonymous sessions

Format: list

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

This is displayed as:

No results 

[[TicketQuery(id=123)]]

This is displayed as:

#123
Typo in the model_api/#field-types

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:

Uncategorized

2048 / 2048
Bug

10712 / 11082
New feature

3903 / 4299
Cleanup/optimization

5642 / 5965

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:

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

1 2 3 4 5 6 7 8 9 10 11 →
Ticket Resolution Summary Owner Reporter
#37385 invalid ASGI client disconnects log "CancelledError exception in shielded future" on Python 3.14+ Carlton Gibson Natalia Bidart
Description

Since ​a013c821ea (#37177), built-in middleware are sync-only, so under ASGI the default middleware chain runs in a thread and calls the view back through async_to_sync(). On Python 3.14+, a client disconnecting while the view is still running makes the asyncio logger emit an ERROR with a traceback: 

CancelledError exception in shielded future
...
  File ".../asgiref/sync.py", line 526, in __call__
    ret = await asyncio.shield(exec_coro)
asyncio.exceptions.CancelledError

The request itself is handled correctly. Python 3.14 changed asyncio.shield() to log the shielded future's exception if the outer task was cancelled, and asgiref's SyncToAsync shields the executor future, which ends with CancelledError when the handler cancels the request.

To reproduce, in a startproject project with the default MIDDLEWARE, add: 

async def slow_async(request):
    await asyncio.sleep(3)
    return HttpResponse("ok")


def slow_sync(request):
    time.sleep(3)
    return HttpResponse("ok")


urlpatterns += [
    path("slow-async/", slow_async),
    path("slow-sync/", slow_sync),
]

Serve it with an async server (uvicorn mysite.asgi:application) and run curl --max-time 1 http://127.0.0.1:8000/slow-async/ (or /slow-sync/). The traceback is logged once the view finishes. The asgi tests also show it (./runtests.py asgi --parallel=1), though they pass.

#37381 fixed Invalid module references in the documentation David Smith Tim Schilling
Description

This ticket is for David Smith's ​PR which covers a few cases where the module references are incorrect in the documentation. I created the ticket to help signal to others that this can be picked up.

I used Claude to determine the following errors still need to be fixed. The rest from David's work were merged in other changes.

File: docs/internals/deprecation.txt:945 Current (wrong): django.template.backends.base.Template.render() Should be: django.template.base.Template.render() ──────────────────────────────────────── File: docs/ref/templates/api.txt:37 Current (wrong): django.template.backends.base.Template.render Should be: django.template.base.Template.render ──────────────────────────────────────── File: docs/releases/1.10.txt:1320 Current (wrong): django.template.backends.base.Template.render Should be: django.template.base.Template.render ──────────────────────────────────────── File: docs/topics/templates.txt:369 Current (wrong): django.template.backends.base Should be: django.template.base ──────────────────────────────────────── File: docs/releases/2.0.txt:283 Current (wrong): django.db.backends.base.DatabaseWrapper.execute_wrapper Should be: django.db.backends.base.base.BaseDatabaseWrapper.execute_wrapper ──────────────────────────────────────── File: docs/topics/db/instrumentation.txt:99 Current (wrong): django.db.backends.base.DatabaseWrapper Should be: django.db.backends.base.base.BaseDatabaseWrapper

#37378 fixed Extra empty breadcrumb in admindocs model_index.html Natalia Bidart Jacob Walls
Description

This HTML typo creates an extra <li> and very likely an extra breadcrumb. Visual regression in bc03f1064e10fa247a46d4e8a98ba9b26aa4790d.

  • django/contrib/admindocs/templates/admin_doc/model_index.html 

    diff --git a/django/contrib/admindocs/templates/admin_doc/model_index.html b/django/contrib/admindocs/templates/admin_doc/model_index.html
index 590cb34b95..82f0a9cb8a 100644
    a b  
    66{% block breadcrumbs %}
    77<ol class="breadcrumbs">
    88<li><a href="{% url 'admin:index' %}">{% translate 'Home' %}</a></li>
    9 <li><a href="{% url 'django-admindocs-docroot' %}">{% translate 'Documentation' %}</a><li>
     9<li><a href="{% url 'django-admindocs-docroot' %}">{% translate 'Documentation' %}</a></li>
    1010<li aria-current="page">{% translate 'Models' %}</li>
    1111</ol>
    1212{% endblock %}
1 2 3 4 5 6 7 8 9 10 11 →

See also: TracQuery, TracTickets, TracReports

Last modified 3 years ago Last modified on Jan 24, 2024, 9:58:09 AM
Note: See TracWiki for help on using the wiki.
Back to Top