Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified criteria.

To configure and execute a custom query, switch to the View Tickets module from the navigation bar, and select the Custom Query link.


When you first go to the query page, the default filter will display tickets relevant to you:

  • If logged in then all open tickets, it will display open tickets assigned to you.
  • If not logged in but you have specified a name or email address in the preferences, then it will display all open tickets where your email (or name if email not defined) is in the CC list.
  • If not logged in and no name/email is defined in the preferences, then all open issues are displayed.

Current filters can be removed by clicking the button to the left with the minus sign on the label. New filters are added from the pulldown lists at the bottom corners of the filters box; 'And' conditions on the left, 'Or' conditions on the right. Filters with either a text box or a pulldown menu of options can be added multiple times to perform an Or on the criteria.

You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket.

After you have edited your filters, click the Update button to refresh your results.

Some shortcuts can be used to manipulate checkbox filters.

  • Clicking on a filter row label toggles all checkboxes.
  • Pressing the modifier key while clicking on a filter row label inverts the state of all checkboxes.
  • Pressing the modifier key while clicking on a checkbox selects the checkbox and deselects all other checkboxes in the filter.

The modifier key is platform and browser dependent. On Mac the modified key is Option/Alt or Command. On Linux the modifier key is Ctrl + Alt. Opera on Windows seems to use Ctrl + Alt, while Alt is effective for other Windows browsers.

Clicking on one of the query results will take you to that ticket. You can navigate through the results by clicking the Next Ticket or Previous Ticket links just below the main menu bar, or click the Back to Query link to return to the query page.

You can safely edit any of the tickets and continue to navigate through the results using the Next/Previous/Back to Query links after saving your results. When you return to the query any tickets which were edited will be displayed with italicized text. If one of the tickets was edited such that it no longer matches the query criteria , the text will also be greyed. Lastly, if a new ticket matching the query criteria has been created, it will be shown in bold.

The query results can be refreshed and cleared of these status indicators by clicking the Update button again.

Saving Queries

Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have Updated the view and then click the Save query button displayed beneath the results. You can also save references to queries in Wiki content, as described below.

Note: one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click Save query. This will build the query string for you. All you need to do is remove the extra line breaks.

Note: you must have the REPORT_CREATE permission in order to save queries to the list of default reports. The Save query button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.

You may want to save some queries so that you can come back to them later. You can do this by making a link to the query from any Wiki page.

[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]

Which is displayed as:

Active tickets against 1.0

This uses a very simple query language to specify the criteria, see Query Language.

Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading ? character:

[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]

Which is displayed as:

Assigned tickets by owner

Customizing the table format

You can also customize the columns displayed in the table format (format=table) by using col=<field>. You can specify multiple fields and what order they are displayed in by placing pipes (|) between the columns:


This is displayed as:

Full rows

In table format you can also have full rows by using rows=<field>:


This is displayed as:

Results (1 - 3 of 27966)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#30118 wontfix Add support for filter arguments in queryset.exists() and queryset.count() nobody Sjoerd Job Postmus

Currently, both .exists() and .count() do not support any arguments.

I would very much enjoy being able to write

if SomeModel.objects.exists(field=value):

instead of

if SomeModel.objects.filter(field=value).exists():

and similarly for count.

Especially when the "search" part of the query is more complex, it would allow one to write

number_of_superusers_in_group = User.objects.count(

which I find visually more appealing over

number_of_superusers_in_group = User.objects.filter(

because of the strange "method-call" on the last line.

As it seems fairly obvious to me, and also fairly simple to implement, I suspect there might be something I'm missing as to why it's not a good idea, and it might already have been documented, but I can not find it.

#30114 invalid ValidationError sometimes raised for valid UUIDs with mod_wsgi nobody Jerry Vinokurov

Our project uses UUIDs as primary keys on a number of models. This works as expected for the majority of the time, but at some point, we run into the following error:

ValidationError: ["'f0c9eb37-a073-47b5-bbb1-589920939c5e' is not a valid UUID."]

This is in fact a valid UUID and also a UUID in our system. We use Sentry for our error reporting, which gives the entire stack trace:

ValidationError: ["'670e5eaf-d231-305e-bb5b-8c8fb0262574' is not a valid UUID."]
  File "django/core/handlers/", line 34, in inner
    response = get_response(request)
  File "django/core/handlers/", line 126, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "django/core/handlers/", line 124, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "python3.6/", line 52, in inner
    return func(*args, **kwds)
  File "django/contrib/admin/", line 604, in wrapper
    return self.admin_site.admin_view(view)(*args, **kwargs)
  File "django/utils/", line 142, in _wrapped_view
    response = view_func(request, *args, **kwargs)
  File "django/views/decorators/", line 44, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
  File "django/contrib/admin/", line 223, in inner
    return view(request, *args, **kwargs)
  File "django/utils/", line 45, in _wrapper
    return bound_method(*args, **kwargs)
  File "django/utils/", line 142, in _wrapped_view
    response = view_func(request, *args, **kwargs)
  File "django/contrib/admin/", line 1792, in changelist_view
    'selection_note': _('0 of %(cnt)s selected') % {'cnt': len(cl.result_list)},
  File "django/db/models/", line 250, in __len__
  File "django/db/models/", line 1188, in _fetch_all
  File "django/db/models/", line 723, in _prefetch_related_objects
    prefetch_related_objects(self._result_cache, *self._prefetch_related_lookups)
  File "django/db/models/", line 1569, in prefetch_related_objects
    obj_list, additional_lookups = prefetch_one_level(obj_list, prefetcher, lookup, level)
  File "django/db/models/", line 1682, in prefetch_one_level
    prefetcher.get_prefetch_queryset(instances, lookup.get_current_queryset(level)))
  File "django/contrib/contenttypes/", line 194, in get_prefetch_queryset
  File "django/db/models/", line 268, in __iter__
  File "django/db/models/", line 1186, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "django/db/models/", line 54, in __iter__
    results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
  File "django/db/models/sql/", line 1052, in execute_sql
    sql, params = self.as_sql()
  File "django/db/models/sql/", line 464, in as_sql
    where, w_params = self.compile(self.where) if self.where is not None else ("", [])
  File "django/db/models/sql/", line 390, in compile
    sql, params = node.as_sql(self, self.connection)
  File "django/db/models/sql/", line 81, in as_sql
    sql, params = compiler.compile(child)
  File "django/db/models/sql/", line 390, in compile
    sql, params = node.as_sql(self, self.connection)
  File "django/db/models/", line 355, in as_sql
    return super().as_sql(compiler, connection)
  File "django/db/models/", line 163, in as_sql
    rhs_sql, rhs_params = self.process_rhs(compiler, connection)
  File "django/db/models/", line 339, in process_rhs
    sqls, sqls_params = self.batch_process_rhs(compiler, connection, rhs)
  File "django/db/models/", line 231, in batch_process_rhs
    pre_processed = super().batch_process_rhs(compiler, connection, rhs)
  File "django/db/models/", line 51, in batch_process_rhs
    _, params = self.get_db_prep_lookup(rhs, connection)
  File "django/db/models/", line 186, in get_db_prep_lookup
    if self.get_db_prep_lookup_value_is_iterable else
  File "django/db/models/", line 185, in <listcomp>
    [get_db_prep_value(v, connection, prepared=True) for v in value]
  File "django/db/models/fields/", line 2316, in get_db_prep_value
    value = self.to_python(value)
  File "django/db/models/fields/", line 2330, in to_python
    params={'value': value},

Ok, so what's going on near line 2330 in django/db/models/fields/ in the to_python function?

2325:                return uuid.UUID(value)
2326:            except (AttributeError, ValueError):
2327:                raise exceptions.ValidationError(
2328:                    self.error_messages['invalid'],
2329:                    code='invalid',
2330:                    params={'value': value},
2331:                )
2332:        return value
2333:    def formfield(self, **kwargs):
2334:        return super().formfield(**{

And what's going on one frame before that, near line 2316 in django/db/models/fields/ in get_db_prep_value:

2312:    def get_db_prep_value(self, value, connection, prepared=False):
2313:        if value is None:
2314:            return None
2315:        if not isinstance(value, uuid.UUID):
2316:            value = self.to_python(value)
2317:        if connection.features.has_native_uuid_field:
2318:            return value
2319:        return value.hex

Ok, so what's happening is that if the value that we're trying to convert is not an instance of uuid.UUID, then we convert it to a Python value, which calls to_python. This makes sense if value is a string, but... Sentry is telling me that value is already a UUID:

value UUID('f0c9eb37-a073-47b5-bbb1-589920939c5e')

The check on line 2315 in get_db_prep_value should catch the fact that this is a UUID, but it doesn't. I don't understand why at all. Sentry is telling me that this is a UUID but it's failing the instance check; as a result line 2325 in to_python attempts to convert the value to a UUID, but value is already a UUID, so it throws a ValidationError.

That's the details of the error. The very weird thing about it is that this error is totally inconsistent in when it shows up. We'll be running for days in a production environment without any problems and then all of a sudden this error will crop up. Once that happens, any attempt to deserialize a UUID fails with this error.

We are running our application on an EC2 instance in AWS managed by Elastic Beanstalk. A deployment of the application, which restarts it, makes this error go away. But sooner or later it crops up again and brings everything down. The worst thing is that I can't seem to replicate this error in local development. Our DB runs on an RDS instance and I can point my local development environment to that DB but I can't replicate the error.

I'm truly baffled by this. Does anyone have any idea how this can happen? It very much seems like a bug to me, hence this report, but I honestly don't know. I'm just hoping to get some guidance or ideas about what is going on here.

#30113 duplicate Ignoring body with application/json payload causes HTTP 400 nobody Yoan Mollard
  1. Create an example view with Django 2.1.4 that does not consume the request's body:
    def myview(request):
        return HttpResponse()
  1. Now send a a first POST with application/json content type, e.g. with axios:"/myview", {"some": "data"})
  1. Send new identical POST requests, and observe that they cause HTTP 400 errors:
    [17/Jan/2019 22:27:47] "POST /myview HTTP/1.1" 200 0
    [17/Jan/2019 22:27:48] "{"some":"data"}POST /myview HTTP/1.1" 200 0
    [17/Jan/2019 22:29:44] code 400, message Bad request syntax ('{"some":"data"}')
    [17/Jan/2019 22:29:44] "{"some":"data"}" 400 -

The JSON payload of the first request is still buffered somewhere and mess up later requests.

  1. Now comment out the print function in the view, and see that consuming the payload has fixed the issue
1 2 3 4 5 6 7 8 9 10 11

Query Language

query: TracLinks and the [[TicketQuery]] macro both use a mini “query language” for specifying query filters. Filters are separated by ampersands (&). Each filter consists of the ticket field name, an operator and one or more values. More than one value are separated by a pipe (|), meaning that the filter matches any of the values. To include a literal & or | in a value, escape the character with a backslash (\).

The available operators are:

= the field content exactly matches one of the values
~= the field content contains one or more of the values
^= the field content starts with one of the values
$= the field content ends with one of the values

All of these operators can also be negated:

!= the field content matches none of the values
!~= the field content does not contain any of the values
!^= the field content does not start with any of the values
!$= the field content does not end with any of the values

The date fields created and modified can be constrained by using the = operator and specifying a value containing two dates separated by two dots (..). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be omitted to avoid having to quote the query string.

created=2007-01-01..2008-01-01 query tickets created in 2007
created=lastmonth..thismonth query tickets created during the previous month
modified=1weekago.. query tickets that have been modified in the last week
modified=..30daysago query tickets that have been inactive for the last 30 days

See also: TracTickets, TracReports, TracGuide, TicketQuery

Last modified 2 years ago Last modified on 09/20/2016 12:24:13 PM
Back to Top