Version 7 (modified by trac, 3 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 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 23936)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#25837 invalid migration fails when there is initial option set on form field nobody kaselis

It requires some setup to reproduce it, but essentially: create a new project, create a new app, create a simple form, for example:

from .models import Item

class ReportForm(forms.Form):
    items = forms.ModelMultipleChoiceField(
        initial=[item for item in Item.objects.all()])

Import that form in the view and that view in urls and migration starts to fail, complaining about missing table (django.db.utils.OperationalError: no such table: myapp_item). It does work fine in django 1.8. Attaching sample project. Tested on django 1.9rc2 (dropdown doesn't have that version to select)

#25835 fixed remove backwards-compatibility alias `Adaptor` sir-sigurd sir-sigurd

All spatial operations classes have Adaptor class attribute and comments say that it backwards-compatibility alias for Adapter. This attribute was added to fix #13315.

It seems however that it doesn't provide any backwards-compatibility. Quoting comment from mentioned ticket:

It's a matter of debate to whether this is a backwards-incompatible change -- the root cause of the issue is that SpatialBackend (and SpatialBackend.Adaptor) no longer exists due to multiple-database support, however, it was never documented to begin with.

I did indeed rename the Adaptor objects to the more common spelling of Adapter; providing aliases is a possibility -- however, I also changed the root namespace to django.contrib.gis.db.backends (the s was added), thus even the aliases wouldn't even be truly backwards-compatible.

As could be seen from comments of that ticket it was proposed to add this alias to deprecation timeline, but for some reason this wasn't done.

#25834 invalid Better expose ORM grouping semantics nobody rtpg

Currently, what QuerySet's annotate does is entirely dependent on opaque semantics that don't hold up to well when working on more complex situations.

Let's say I have a LineItem model (the line items of an invoice, for example) that I want to calculate some stats on, with a price, and a price_currency. Some pointy haired boss wants to know what the totals on the line items are depending on currency. Pull out my nifty annotate tool:

In [33]: print LineItem.objects.values('price_currency').annotate(total=Sum('price'))
[{'price_currency': u'USD', 'total': Decimal('9001')}]

So there annotate ends up putting things into the GROUP BY clause to do the sum (namely the previous values call)

Sometimes I just want to rename columns to make my life easier, so I'll make a pc field as a shortcut to price:

In[37]: print LineItem.objects.values('price_currency').annotate(pc=F('price'))
[{'price_currency': u'USD', 'pc': Decimal('0')}, {'price_currency': u'USD', 'pc': Decimal('34')}, ...etc...]

Here annotate adds a SELECT clause without touching the GROUP BY clause

When I end up working on a bigger query, I'll try to simplify my queryset expression after I have something that computes what I wanted, so doing things like merging filters and, sometimes annotate:

In[39]: print LineItem.objects.values('price_currency').annotate(total=Sum('price'), pc=F('price')).query

SELECT "item_lineitem"."price_currency", SUM("item_lineitem"."price") AS "total" FROM "item_lineitem" GROUP BY "item_lineitem"."price_currency", "item_lineitem"."price" ORDER BY "item_lineitem"."position" ASC

So when I annotate with a mixture of "grouping required" and "adding a select" , then everything becomes "grouping required", and in the previous example, suddenly I'm grouping by currency AND price. I think this is the only valid behaviour if you want to return something, but shouldn't this just fail?

(Some crazier stuff is when you annotate with Sum and it simply groups by _all_ of your model's fields. I think the reason this doesn't fail is for the motivating example in the documentation (of counting the min price of the books in a store), but this seems like something that should fail)

My understanding is that Django's ORM is coming more to terms with the fact that it's basically always going to be paired with a RDBMS, so this multi-meaning annotate being the only reasonable way to use grouping is a hard sell to me. I very much want to get rid of all of our custom SQL, but I have to spend a day working on one query, all because annotate ends up being 2 separate functions:

  • "group by previous values call and add aggregation function to select"
  • "add a select clause"

Not to mention that the pairing with values means that if I want to group by a complex query, I have to do something like:


in order to actually have the grouping_property to show up in the select (values doesn't work on some of my annotated values for some reason... there might be a bug that I haven't successfully isolated in my code or the ORM).

Anyways, I'm complaining about this because I would much rather have errors show up for a lot of these cases, so that I can at least fix them, but in the current API that would be impossible...

In my ideal world, you would have group(by=columns_or_expressions, into=aggregation_things) which would be somewhat equivalent to "group by the columns in by (something like values), and annotate your select with the into clause)", so when someone asks how to do a grouping you can point to that directly. And annotate would be relegated to only touching the SELECT part of a query. With backwards compatability considerations, you could probably make a separate method just for SELECT.

I'm not sure of the implications with regards to joins and things like annotate(Sum('books__price')), but my impression is that all this functionality is in the ORM already, just all within annotate

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

Back to Top