Version 7 (modified by trac, 12 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.

Filters

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.

Example:

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

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:

[[TicketQuery(id=123)]]

This is displayed as:

#123
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:

0

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:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Full rows

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

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]

This is displayed as:

Results (1 - 3 of 33584)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#35316 wontfix Support scalars as query parameters in admin changelist filters (for backward compatibility). nobody Manolis Stamatogiannakis
Description

Ticket #1873 added support for multi-valued query parameters in admin changelist filters. Because only list types are supported, older code that e.g. extends SimpleListFilter or BooleanFieldListFilter will break.

The latter (extending BooleanFieldListFilter) may even be completely unsupported. See notes in PR for #1873.

Overall, user code needs to introduce version conditionals if it is required to support both Django 4.x and Django 5. The reason is that Django 4.x only supports scalar types as query parameter values, while Django 5 only supports lists.

Since supporting both scalars and lists should be possible without adding complexity to the Django codebase, it would be good to continue supporting scalars, perhaps with a deprecation warning, if necessary.

#35315 invalid 5.0.3: pytest fails with tons of ImportErrors nobody Tomasz Kłoczko
Description

On testing I'm using python 3.9.18 and pytest 8.1.1. Looks like on scanning units pytest fails +500 errors like below

==================================== ERRORS ====================================
________ ERROR collecting tests/admin_changelist/test_date_hierarchy.py ________
ImportError while importing test module '/home/tkloczko/rpmbuild/BUILD/django-5.0.3/tests/admin_changelist/test_date_hierarchy.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib64/python3.9/importlib/__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/admin_changelist/test_date_hierarchy.py:3: in <module>
    from django.contrib.admin.options import IncorrectLookupParameters
../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-packages/django/contrib/admin/__init__.py:2: in <module>
    from django.contrib.admin.filters import (
../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-packages/django/contrib/admin/filters.py:12: in <module>
    from django.contrib.admin.options import IncorrectLookupParameters
../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-packages/django/contrib/admin/options.py:10: in <module>
    from django import forms
../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-packages/django/forms/__init__.py:6: in <module>
    from django.forms.boundfield import *  # NOQA
../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-packages/django/forms/boundfield.py:4: in <module>
    from django.forms.utils import RenderableFieldMixin, pretty_name
../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-packages/django/forms/utils.py:6: in <module>
    from django.forms.renderers import get_default_renderer
../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-packages/django/forms/renderers.py:6: in <module>
    from django.template.backends.django import DjangoTemplates
../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-packages/django/template/__init__.py:44: in <module>
    from .engine import Engine
../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-packages/django/template/engine.py:7: in <module>
    from .base import Template
../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-packages/django/template/base.py:60: in <module>
    from django.utils.html import conditional_escape, escape
../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-packages/django/utils/html.py:11: in <module>
    from django.utils.encoding import punycode
../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-packages/django/utils/encoding.py:5: in <module>
    from types import NoneType
E   ImportError: cannot import name 'NoneType' from 'types' (/usr/lib64/python3.9/types.py)
#35314 duplicate Django 5 breaks value of Date field rendering correctly in template nobody Michael
Description

This used to work correctly in Django 4. Django 5 removed USE_L10N setting from settings.py

When rendering an input field that is of type date:

  /home/michael/.venv/project/lib/python3.11/site-packages/django/forms/boundfield.py(108)as_widget()
-> return widget.render(
  /home/michael/.venv/project/lib/python3.11/site-packages/django/forms/widgets.py(279)render()
-> context = self.get_context(name, value, attrs)
  /home/michael/.venv/project/lib/python3.11/site-packages/django/forms/widgets.py(332)get_context()
-> context = super().get_context(name, value, attrs)
  /home/michael/.venv/project/lib/python3.11/site-packages/django/forms/widgets.py(271)get_context()
-> "value": self.format_value(value),
  /home/michael/.venv/project/lib/python3.11/site-packages/django/forms/widgets.py(555)format_value()
-> value, self.format or formats.get_format(self.format_key)[0]

We see that formats.get_format(self.format_key) only passes in 1 argument to:

# django/utils/formats.py(109)get_format()

def get_format(format_type, lang=None, use_l10n=None):
    """
    For a specific format type, return the format for the current
    language (locale). Default to the format in the settings.
    format_type is the name of the format, e.g. 'DATE_FORMAT'.

    If use_l10n is provided and is not None, it forces the value to
    be localized (or not), otherwise it's always localized.
    """
    if use_l10n is None:
        use_l10n = True
    if use_l10n and lang is None:
        lang = get_language()
    format_type = str(format_type)  # format_type may be lazy.
    cache_key = (format_type, lang)
    try:
        return _format_cache[cache_key]
    except KeyError:
        pass

this means use_l10n initial value is None, which means it will be set to True via the logic:

    if use_l10n is None:
        use_l10n = True

So then it sets a language, in my case en-gb, which makes results in a cache_key of ('DATE_INPUT_FORMATS', 'en-gb')

Which means the get_format method returns ['%d/%m/%Y', '%d/%m/%y', '%Y-%m-%d'] Which is really bad when format_type = 'DATE_INPUT_FORMATS', because HTML inputs must always be in the format YYYY/MM/DD, and hence selecting the first format of %d/%m/%Y results in an error in your HTML template when your input is rendered like <input type="date" value="31/12/2024"> instead of <input type="date" value="2024/12/31">

Not that it changes anything, but here is my DATE_INPUT_FORMATS from settings.py (it has no USE_L10N setting as unfortunately that has been removed):

DATE_INPUT_FORMATS = [
    '%Y-%m-%d',
]
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

Note: See TracWiki for help on using the wiki.
Back to Top