Version 6 (modified by trac, 8 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 27865)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#30032 duplicate Can't alter the default of a DateTimeField to be TransactionNow nobody Gavin Wahl

I have this field:

    foo = models.DateTimeField(

I would like to modify it to use TransactionNow instead:

    foo = models.DateTimeField(default=TransactionNow())

This migration operation is generated:


When run, this error is thrown:

  File "./", line 29, in <module>
  File "django/core/management/", line 381, in execute_from_command_line
  File "django/core/management/", line 375, in execute
  File "django/core/management/", line 316, in run_from_argv
    self.execute(*args, **cmd_options)
  File "django/core/management/", line 353, in execute
    output = self.handle(*args, **options)
  File "django/core/management/", line 83, in wrapped
    res = handle_func(*args, **kwargs)
  File "django/core/management/commands/", line 203, in handle
  File "django/db/migrations/", line 117, in migrate
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
  File "django/db/migrations/", line 147, in _migrate_all_forwards
    state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
  File "django/db/migrations/", line 244, in apply_migration
    state = migration.apply(state, schema_editor)
  File "django/db/migrations/", line 124, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
  File "django/db/migrations/operations/", line 216, in database_forwards
    schema_editor.alter_field(from_model, from_field, to_field)
  File "django/db/backends/base/", line 523, in alter_field
    old_db_params, new_db_params, strict)
  File "django/db/backends/postgresql/", line 122, in _alter_field
    new_db_params, strict,
  File "django/db/backends/base/", line 626, in _alter_field
    old_default = self.effective_default(old_field)
  File "django/db/backends/base/", line 239, in effective_default
    return field.get_db_prep_save(default, self.connection)
  File "django/db/models/fields/", line 790, in get_db_prep_save
    return self.get_db_prep_value(value, connection=connection, prepared=False)
  File "django/db/models/fields/", line 1429, in get_db_prep_value
    value = self.get_prep_value(value)
  File "django/db/models/fields/", line 1408, in get_prep_value
    value = super().get_prep_value(value)
  File "django/db/models/fields/", line 1268, in get_prep_value
    return self.to_python(value)
  File "django/db/models/fields/", line 1369, in to_python
    parsed = parse_datetime(value)
  File "django/utils/", line 106, in parse_datetime
    match = datetime_re.match(value)
TypeError: expected string or bytes-like object

If I create the field foo from scratch, with an AddField operation instead of AlterField, it works as expected.

I should be able to modify a field to use TransactionNow() as a default.

#30029 wontfix Generate migration dependencies in a deterministic order Dakota Hawkins Dakota Hawkins

From this google groups discussion:

We haven't really deployed yet, so generally to make migrations we're deleting existing migration files and re-running makemigrations.

We have two apps, and one of them depends on the other as well as django.contrib.auth. In that app's migrations the dependencies often swap order seemingly indeterminately.

The resulting migration includes either:

class Migration(migrations.Migration):
    initial = True
    dependencies = [
        ('auth', '0009_alter_user_last_name_max_length'),
        ('app2', '0001_initial'),


class Migration(migrations.Migration):
    initial = True
    dependencies = [
        ('app2', '0001_initial'),
        ('auth', '0009_alter_user_last_name_max_length'),

and it seems to switch back and forth with nearly every run.

Does anybody know why, or how to nail down the order? It doesn't seem to make a technical difference, but I'd like to avoid the churn/noise in our repo.

According to Simon Charette in that discussion:

It should be a simple matter of using sorted in MigrationWriter.as_string[0].

I poked around the code a bit, in hopes of first writing a failing unit test and then fixing the issue, but I'm not sure how to write the test with multiple interdependent apps since temporary_migration_module seems to support only a single app. Another concern is that the test may be flaky since the current order is indeterminate... it may take some arbitrary number of iterations to be reasonably certain the case could have been reproduced by one of them.

I'd be happy to investigate further if somebody could help me get started with some advice on writing that test.

#30022 wontfix Doc how to combine post_save signal with on_commit to alter a m2m relation when saving a model instance nobody George Tantiras

Trying to alter a many to many relation when saving a model's instance is a common use case.

For example, when creating a new user or altering an already existing user, programmatically add or remove groups he should(n't) belong to.

This can be achieved by catching a post save signal and creating a decorator that uses on_commit:

def on_transaction_commit(func):
    ''' Create the decorator '''
    def inner(*args, **kwargs):
        transaction.on_commit(lambda: func(*args, **kwargs))

    return inner

def group_delegation(instance, raw, **kwargs):
    do stuff()

Is it relevant to doc it as an example in the post_save signal chapter?

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