Version 9 (modified by trac, 8 years ago) ( diff )

--

Trac Ticket Queries

Table of Contents

In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified 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 in and no name/email is 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 on 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.

After you have edited your filters, click the Update button to refresh your results.

Some shortcuts can be used to manipulate checkbox filters.

  • Clicking on a filter row label toggles all checkboxes.
  • Pressing the modifier key while clicking on a filter row label inverts the state of all checkboxes.
  • Pressing the modifier key while clicking on a checkbox selects the checkbox and deselects all other checkboxes in the filter.

The modifier key is platform and browser dependent. On Mac the modified key is Option/Alt or Command. On Linux the modifier key is Ctrl + Alt. Opera on Windows seems to use Ctrl + Alt, while Alt is effective for other Windows browsers.

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

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

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

[[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 34124)

1 2 3 4 5 6 7 8 9 10 11 →
Ticket Resolution Summary Owner Reporter
#35929 invalid Unable to login using superuser account with 5.1.3 default install R Murthy
Description

I have created new python virtual environment to work on django version 5.1.3. Created a new superuser called admin. Run the server. Open the browser to ​http://127.0.0.1:8000/admin. Login with the user, admin and password input at the creation time. It throws an error, "Please enter the correct username and password for a staff account. Note that both fields may be case-sensitive."

Start the shell to verify the superuser settings, it shows the admin user has staff, superuser, and active set.

Use the shell to create another superuser, test. Set the staff, superuser, and active flags. On the browser, login using the new superuser account, test. It logs you in. Reset the 'admin' superuser by unchecking the staff, superuser, and active boxes. Save. Check the boxes. Save. Log out of 'test' superuser account. Login using 'admin' superuser account. Success. I suspect there is an issue with the createsuperuser script. Can you please let me know?

Also, I could not find any documentation on viewing account details using the shell. It is possible I may have missed it when I ran a search on the documentation. If it is there and I missed it, my apologies.

Environment: Windows 11 Pro, Python 3.1.3, django 5.1.3, Microsoft Edge Browser Version 131.0.2903.51 (Official build) (64-bit)

Running Environment: 

py --version
Python 3.13.0

py -m pip list
Package      Version
------------ -------
asgiref      3.8.1
distlib      0.3.9
Django       5.1.3
filelock     3.16.1
pip          24.3.1
platformdirs 4.3.6
sqlparse     0.5.2
tzdata       2024.2
virtualenv   20.27.1

Commands run on the shell: 

>>> from django.contrib.auth.models import User
>>> usr=User.objects.get(username='admin')
>>> usr.is_staff
True
>>> usr.is_superuser
True
>>> usr.is_active
True
>>> usr=User.objects.create_user('test', 'test@localhost', 'test123')
>>> usr.save()
>>> usr.is_superuser
False
>>> usr.is_superuser=True
>>> usr.is_active
True
>>> usr.is_staff
False
>>> usr.is_staff=True
>>> usr.save()
>>> ^Z

now exiting InteractiveConsole...

Please note that other than running the migrate and createsuperuser commands to enable superuser account, there are no changes made to the default install.

If I have missed any other relevant information, kindly contact me. Thanks for looking into this issue.

#35928 duplicate [contenttypes] GenericRelation uses wrong primary key type if set to models.UUIDField Jon Eyolfson
Description

For a minimal example, if I have the following: 

class Delivery(models.Model):

    id = models.UUIDField(primary_key=True, editable=False)
    content_type = models.ForeignKey(
        ContentType,
        on_delete=models.CASCADE,
        null=True,
        blank=True,
        editable=False,
    )
    object_id = models.PositiveBigIntegerField(
        blank=True,
        null=True,
        editable=False,
    )
    content_object = GenericForeignKey("content_type", "object_id")

class Other(models.Model):

    delivery = GenericRelation(Delivery, related_query_name="other")

If I use delivery.other.all().query I see the wrong primary key: 

SELECT /* SNIP */ WHERE "delivery"."id" = 269290806699601176541887178676879701060

If I look at a normal query with the primary key on Delivery, like Delivery.objects.filter(pk=delivery_pk).query, I see: 

SELECT /* SNIP */ WHERE "delivery"."id" = ca9785d8a6e311ef874b0ad61d0b3444

This causes SQLite to show the following error: 

OverflowError: Python int too large to convert to SQLite INTEGER

I assume because GenericRelation is converting the UUID to an integer, which would cause the lookup to fail anyways.

#35927 invalid utils/encoding.py force_string, smart_string, force_bytes, and smart_bytes should verify encoding parameter is not None Derek Knowlton Derek M. Knowlton
Description

Overview

The force_str(), force_bytes(), smart_str(), smart_bytes() functions in django/utils/encoding.py currently doesn't verify that the encoding parameter is not None. When None is passed as the encoding parameter and the input is bytes, it results in a TypeError from Python's built-in str() function rather than providing a clear validation error.

Reproduction

from django.utils.encoding import force_str

# This raises TypeError: str() argument 'encoding' must be str, not None
result = force_str(b'test', encoding=None)

Behaviors

Current Behavior:

  • When encoding=None is passed by input, a TypeError is raised by Python's built-in str() function
  • The error message from this specific error does not indicate that the error originated from utils/encoding.py, or that the error comes from an incorrect value passed to the functions inside utils/encoding.py
  • No upfront validation is performed on the encoding parameter

Expected Behavior:

  • Early detection of invalid encoding parameter
  • Custom TypeError with a descriptive message if None is passed
  • Follows explicit parameter validation principles

Suggested Fix

if encoding is None:
    raise TypeError("{{function name}}: encoding parameter cannot be None")

Summary

Though this change is small, it would improve developer experience by increasing the accuracy of error handling. This change is backwards compatible as it does not change the functionality of the code as passing None was never valid.

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. Filters are separated by ampersands (&). Each filter 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 omitted 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, TicketQuery

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