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 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 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.

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

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. This also allows displaying the link and description of a single ticket:


This is displayed as:

Typo in the model_api/#field-types

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, use 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 24873)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#26801 duplicate Queryset gets corrupted when using nested Prefetch nobody mlubimow

When queryset objects contains nested Prefetch objects, after first evaluation it gets corrupted.

Im attaching simple example, to reproduce a bug you need to run these commands:

  1. Install requirements file
  2. python migrate
  3. python manage runserver

Open your browser on:

And refresh twice. First time its gonna work, next time you should get an error:

AttributeError at /
Cannot find 'author' on UserProfile object, 'author__profile__university' is an invalid parameter to prefetch_related()

From my limited investigation it looks like after first evaluation prefetch_to parameter is prepended with previous prefetch_to param, which is in this case not correct.

Temporarly, its enough to create this object (queryset) again every time it gets used.

#26799 duplicate Model related signals' receiver could not receive its proxy models nobody mapher87

We have to connect the same receiver to its all proxy models one by one

class TestModel(models.Model):
    field1 = models.CharField(max_length=64)
    field2 = models.CharField(max_length=64)

    class Meta:
        db_table = 'app_label_test_model'

class ProxyTestModel(TestModel):
    class Meta:
        proxy = True

from django.db.models.signals import pre_save
def on_test_model_change(sender, instance, **kwargs):
    if not instance.field1.startswith('*'):
        instance.field1 = u'*' + instance.field1
pre_save.connect(on_test_model_change, sender=TestModel)
# pre_save.connect(on_test_model_change, sender=ProxyTestModel)

>>> t = TestModel()
>>> t.field1
>>> pt = ProxyTestModel()
>>> pt.field1

Otherwise, we should consider to split one Model to manage it more conveniently and safely. As there is an attribute 'concrete_model' kept in Model's Option, could we take the benefits of it?

class RealTestModel1(models.Model):
    field1 = models.CharField(max_length=64)
    class Meta:
        managed = False
        db_table = 'app_label_test_model'

class RealTestModel2(models.Model):
    field2 = models.CharField(max_length=64)
    class Meta:
        managed = False
        db_table = 'app_label_test_model'

In my project, i hacked like this for more admin site features which could be implemented in Model's generation process:

from django.db.models.base import ModelBase
from django.dispatch import dispatcher
# for adapting to sub-models
_make_id = dispatcher._make_id
def _new_make_id(target):
    if isinstance(target, ModelBase):
        return id(getattr(target, '_concrete_model', target._meta.concrete_model))
    return _make_id(target)

dispatcher._make_id = _new_make_id

# ...

class ABSModelBase(ModelBase):
    Abstract Meta-Class to make new model performs as concrete model

    _concrete_model = ModelBase

    def __subclasscheck__(cls, subclass):
        return issubclass(subclass, cls._concrete_model)

    def __instancecheck__(cls, instance):
        return isinstance(instance, cls._concrete_model)

# ...
    # create new class
    new_class = ABSModelBase.__new__(
        ABSModelBase, name, tuple(bases), attrs,

    # register new_class as subclass of concrete_model
    new_class.__bases__ = (concrete_meta.model, ) + new_class.__bases__
    # register subclass and instance checking
    new_class._concrete_model = concrete_meta.model
#26797 duplicate Reverse `related_name` of a proxy not accessible to inherited proxies in queryset nobody mlorant

Taken the following example (not real world use case, but it is somewhat equivalent of something I encountered):

from django.db import models

class Animal(models.Model):
    name = models.CharField("animal name", max_length=255, blank=True, null=False)

class Mammal(Animal):
    class Meta:
        proxy = True

class Cat(Mammal):
    class Meta:
        proxy = True

class Dog(Mammal):
    class Meta:
        proxy = True

class TrueFriendship(models.Model):
    mammal = models.ForeignKey(Mammal, related_name="dog_friends")
    dog = models.ForeignKey(Dog, related_name="mammal_friends")

I want to get the number of friends of a queryset of cats. However, doing this in a shell results in an exception:

>>> from nature.models import *
>>> cat = Cat.objects.create(name="cat1")
>>> dog = Dog.objects.create(name="dog1")
>>> TrueFriendship.objects.create(cat=cat, dog=dog)
>>> Cat.objects.annotate(nb_dog_friends=models.Count('dog_friends'))
Traceback (most recent call last):
  File "/data/.virtualenvs/bugproxy/local/lib/python2.7/site-packages/django/db/models/", line 122, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/data/.virtualenvs/bugproxy/local/lib/python2.7/site-packages/django/db/models/sql/", line 1330, in names_to_path
    "Choices are: %s" % (name, ", ".join(available)))
FieldError: Cannot resolve keyword 'dog_friends' into field. Choices are: id, name

(Full traceback attached in a file) The same goes for "simple" query such as Cat.objects.filter(dog_friends__isnull=False). However, using the Mammal proxy, both queries work and the reverse relation is available on single Cat object:

>>> Mammal.objects.annotate(nb_dog_friends=models.Count('dog_friends')).first().nb_dog_friends
>>> Cat.objects.first().dog_friends.all()
[<TrueFriendship: TrueFriendship object>]

Something is inconsistent here: I would expect to have access to dog_friends in both cases (on a model instance and a queryset)

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

Last modified 2 years ago Last modified on 02/24/14 07:33:46
Back to Top