Version 6 (modified by trac, 6 years ago) (diff)


Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, used to display lists of tickets meeting a specified set of 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 and no name/email defined in the preferences then all open issues are displayed.

Current filters can be removed by clicking the button to the right 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 of 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.

Once you've edited your filters click the Update button to refresh your results.

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.

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

Using the [[TicketQuery]] Macro

The TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.



This is displayed as:

No results

Just like the query: wiki links, the parameter of this macro expects a query string formatted according to the rules of the simple ticket query language.

A more compact representation without the ticket summaries is also available:

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

This is displayed as:

No results

Finally if you wish to receive only the number of defects that match the query using the count parameter.

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

This is displayed as:


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 by placing pipes (|) between the columns like below:


This is displayed as:

Full rows

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


This is displayed as:

Results (1 - 3 of 25913)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#27885 duplicate Migration creates index of a deleted table nobody ihucos

If we create a model in a migration with an indexed field, then delete that model, migrations will still try to create the index on a nonexistent table.

That scenario occurred after squashing migrations.

Happened on Django 1.8.13

Example Migration that reproduces this:

# -*- coding: utf-8 -*-
from __future__ import unicode_literals

from django.db import migrations, models

class Migration(migrations.Migration):

    dependencies = [
        ('bookoya', '0085_auto_20170214_1425'),

    operations = [
                ('name', models.CharField(max_length=100, unique=True, serialize=False, primary_key=True, db_index=True)),

~/R $ python migrate
Waiting for database...
(0.000) select 1; args=None
Database ready
(0.003) SELECT 1 FROM pg_database WHERE datname = 'template_postgis' LIMIT 1;; args=('template_postgis',)
(0.001) CREATE EXTENSION IF NOT EXISTS postgis; args=None
            SELECT c.relname, c.relkind
            FROM pg_catalog.pg_class c
            LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
            WHERE c.relkind IN ('r', 'v')
                AND n.nspname NOT IN ('pg_catalog', 'pg_toast')
                AND pg_catalog.pg_table_is_visible(c.oid); args=None
(0.005) SELECT "django_migrations"."app", "django_migrations"."name" FROM "django_migrations"; args=()
Operations to perform:
  Synchronize unmigrated apps: checkrequirements, s3_folder_storage, tastypie_oauth, gis, postgres, cacheops, webpack_loader, staticfiles, debug_toolbar, djorm_core, waitfordb, messages, django_otp, django_nose, storages, session_cleanup,
 djorm_hstore, djorm_expressions
  Apply all migrations: oauth2_provider, qmore, admin, oauth_provider, sendgrid, sessions, tastypie, otp_static, flatpages, sites, kombu_transport_django, invoices, contenttypes, bookoya, auth, recommend, otp_totp, two_factor
Synchronizing apps without migrations:
            SELECT c.relname, c.relkind
            FROM pg_catalog.pg_class c
            LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
            WHERE c.relkind IN ('r', 'v')
                AND n.nspname NOT IN ('pg_catalog', 'pg_toast')
                AND pg_catalog.pg_table_is_visible(c.oid); args=None
  Creating tables...
    Running deferred SQL...
  Installing custom SQL...
Running migrations:
  Rendering model states... DONE
  Applying bookoya.0086_auto_20170227_1359...CREATE TABLE "bookoya_mymodel" ("name" varchar(100) NOT NULL PRIMARY KEY); (params None)
(0.025) CREATE TABLE "bookoya_mymodel" ("name" varchar(100) NOT NULL PRIMARY KEY); args=None
DROP TABLE "bookoya_mymodel" CASCADE; (params [])
(0.002) DROP TABLE "bookoya_mymodel" CASCADE; args=[]
DELETE FROM geometry_columns WHERE f_table_name = 'bookoya_mymodel'; (params [])
(0.002) DELETE FROM geometry_columns WHERE f_table_name = 'bookoya_mymodel'; args=[]
CREATE INDEX "bookoya_mymodel_name_e935283cc44e389_like" ON "bookoya_mymodel" ("name" varchar_pattern_ops); (params [])
(0.012) CREATE INDEX "bookoya_mymodel_name_e935283cc44e389_like" ON "bookoya_mymodel" ("name" varchar_pattern_ops); args=[]
Traceback (most recent call last):
  File "", line 47, in <module>
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/", line 354, in execute_from_command_line
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/", line 346, in execute
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/", line 394, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/", line 445, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/", line 222, in handle
    executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
  File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/", line 110, in migrate
    self.apply_migration(states[migration], migration, fake=fake, fake_initial=fake_initial)
  File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/", line 148, in apply_migration
    state = migration.apply(state, schema_editor)
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/base/", line 91, in __exit__
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/base/", line 111, in execute
    cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/", line 79, in execute
    return super(CursorDebugWrapper, self).execute(sql, params)
  File "/usr/local/lib/python2.7/dist-packages/cacheops/", line 86, in execute
    result = self._no_monkey.execute(self, sql, params)
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/dist-packages/django/db/", line 98, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/", line 64, in execute
    return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: relation "bookoya_mymodel" does not exist
#27884 wontfix Document that validators needs to be an iterable since Django 1.11 nobody Thom Wiggers

At one time with Django <1.11 (probably 1.10) someone wrote the following code:

class Bla(Model):
    someint = IntegerField(validators=MinValueValidator(1990))

While he should have used an iterable for validators, note that this worked fine, and Django generated a migration:

operations = [
    migrations.CreateModel(name="Bla", fields=[
         # ...
         ('someint', models.IntegerField(validators=django.core.validators.MinValueValidator(1990))),

However, if this migration is loaded by Django 1.11 when running migrate or makemigrate or whatever, it raises the following exception:

  File "/builds/X/Y/website/Z/migrations/", line 10, in <module>
    class Migration(migrations.Migration):
  File "/builds/X/Y/website/Z/migrations/", line 22, in Migration
    ('someint', models.IntegerField(validators=django.core.validators.MinValueValidator(1990))),
  File "/builds/X/Y/.tox/py34-django11/lib/python3.4/site-packages/django/db/models/fields/", line 183, in __init__
    self._validators = list(validators)  # Store for deconstruction later
TypeError: 'MinValueValidator' object is not iterable

While I understand taking out code that allows for this poor coding style, this will make migrating to Django 1.11 perhaps not trivial for everyone. Simply fixing it in the Model is not enough, this generates a new migration and doesn't yet get rid of the old migration. I think the best way to work around this is to squash the offending migrations before moving to 1.11.

My suggestion is noting this (or a better workaround/fix) in the release notes.

#27879 fixed Writing Atom1Feed crashes if enclosures argument isn't provided to add_item() Pavlo Kapyshin Pavlo Kapyshin

After 75cf9b5ac031feb8f94271c9906157c921a14520 not passing enclosures (leaving default None) to Atom1Feed.add_item() results in a TypeError.

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. Basically, the filters are separated by ampersands (&). Each filter then 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 litteral & or | in a value, escape the character with a backslash (\).

The available operators are:

= the field content exactly matches the 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 left out 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

Back to Top