Trac Ticket Queries

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#32032 duplicate Aggregate on union of querysets generates invalid SQL nobody Jaap Roes
Description

I'm getting the following error when trying to perform an aggregate on a union of querysets:

django.db.utils.ProgrammingError: column "__col1" does not exist
LINE 1: SELECT COALESCE(BOOL_OR("__col1"), false), COALESCE(BOOL_OR(...

What I have are the following models:

class Organisation(models.Model):
    ...

class Partner(models.Model):
    ...

class Entity(models.Model):
    organisation = models.ForeignKey(Organisation)
    partner = models.ForeignKey(Partner, null=True)

A user can have certain permissions on Entities, either directly or through an Organisation or Partner.

class BaseEntityPermissions(models.Model):
    user = models.ForeignKey(User)
    can_discombobulate = models.BooleanField(default=True)
    can_frobnicate = models.BooleanField(default=False)

    class Meta:
        abstract = True

class EntityPermissions(BaseEntityPermissions):
    entity = models.ForeignKey(Entity)

    class Meta:
        unique_together = ('user', 'entity')

class OrganisationEntityPermissions(BaseEntityPermissions):
    organisation = models.ForeignKey(Organisation)

    class Meta:
        unique_together = ('user', 'organisation')

class PartnerEntityPermissions(BaseEntityPermissions):
    partner = models.ForeignKey(Partner)

    class Meta:
        unique_together = ('user', 'partner')

These permissions stack; for example, a user can get the permission to "discombobulate" all Entities of a specific Organisation on the Organisation level and can gain the permission to "frobnicate" a specific Entity.

I therefore wrote this function to get the applicable permissions for a user and an entity:

def get_user_entity_permissions(user, entity):
    querysets = [
        EntityPermissions.objects.filter(
            entity_id=entity.id, user=user
        ).values('can_discombobulate', 'can_frobnicate'),
        OrganisationEntityPermissions.objects.filter(
            organisation_id=entity.organisation_id, user=user
        ).values('can_discombobulate', 'can_frobnicate')
    ]

    if entity.partner_id:
        querysets.append(
            PartnerEntityPermissions.objects.filter(
                partner_id=entity.partner_id, user=user
            ).values('can_discombobulate', 'can_frobnicate')
        )

    qs = functools.reduce(lambda qs1, qs2: qs1.union(qs2), querysets)

    return qs.aggregate(
        can_discombobulate=Coalesce(BoolOr('can_discombobulate'), False),
        can_frobnicate=Coalesce(BoolOr('can_frobnicate'), False)
    )

Sadly, execution this code results in the error previously mentioned.

The full generated SQL is as follows:

SELECT COALESCE(BOOL_OR("__col1"), false), COALESCE(BOOL_OR("__col2"), false) 
FROM (
  (
    SELECT "foo_entitypermissions"."can_discombobulate", "foo_entitypermissions"."can_frobnicate" 
    FROM "foo_entitypermissions" 
    WHERE ("foo_entitypermissions"."user_id" = 1 AND "foo_entitypermissions"."entity_id" = 1)
  ) 
  UNION (
    SELECT "foo_organisationentitypermissions"."can_discombobulate", "foo_organisationentitypermissions"."can_frobnicate" 
    FROM "foo_organisationentitypermissions" 
    WHERE ("foo_organisationentitypermissions"."user_id" = 1 AND "foo_organisationentitypermissions"."organisation_id" = 1)
  )
) subquery

This is almost correct, except for the __col1 and __col2 aliases, which don't exist.

#32030 duplicate Make Token Generator more universal Ilya Chichak Ilya Chichak
Description

I suggest to split current PasswordResetTokenGenerator into BaseTokenGenerator and it's implementation PasswordResetTokenGenerator

To make BaseTokenGenerator more universal, it should contain class variable TOKEN_TIMEOUT with token timeout and _make_hash_value method public and abstract.

It will make possible to make email confirmation tokens, one time enter tokens and other with reimplementing make_hash_value method and setting separate timeout for each token generator. Current PasswordResetTokenGenerator will be implementation of BaseTokenGenerator where TOKEN_TIMEOUT will be settings.PASSWORD_RESET_TIMEOUT. So, for all logic, that uses PasswordResetTokenGenerator nothing will be changed.

https://github.com/django/django/pull/13444

#32026 duplicate AttributeError: 'tuple' object has no attribute 'startswith' 315xiaoyao
Description

manage.py@dev > migrate ssh://root@10.32.109.197:22/proj/env/bin/python3 -u /root/.pycharm_helpers/pycharm/django_manage.py migrate /proj/app/mysite File tracking disabled Operations to perform:

Apply all migrations: admin, auth, cmdb, contenttypes, sessions

Running migrations:

Applying cmdb.0001_initial...Traceback (most recent call last): File "/root/.pycharm_helpers/pycharm/django_manage.py", line 59, in <module>

run_command()

File "/root/.pycharm_helpers/pycharm/django_manage.py", line 46, in run_command

run_module(manage_file, None, 'main', True)

File "/usr/local/python3/lib/python3.8/runpy.py", line 207, in run_module

return _run_module_code(code, init_globals, run_name, mod_spec)

File "/usr/local/python3/lib/python3.8/runpy.py", line 97, in _run_module_code

_run_code(code, mod_globals, init_globals,

File "/usr/local/python3/lib/python3.8/runpy.py", line 87, in _run_code

exec(code, run_globals)

File "/proj/app/mysite/manage.py", line 22, in <module>

main()

File "/proj/app/mysite/manage.py", line 18, in main

execute_from_command_line(sys.argv)

File "/proj/env/lib/python3.8/site-packages/django/core/management/init.py", line 401, in execute_from_command_line

utility.execute()

File "/proj/env/lib/python3.8/site-packages/django/core/management/init.py", line 395, in execute

self.fetch_command(subcommand).run_from_argv(self.argv)

File "/proj/env/lib/python3.8/site-packages/django/core/management/base.py", line 330, in run_from_argv

self.execute(*args, cmd_options)

File "/proj/env/lib/python3.8/site-packages/django/core/management/base.py", line 371, in execute

output = self.handle(*args, options)

File "/proj/env/lib/python3.8/site-packages/django/core/management/base.py", line 85, in wrapped

res = handle_func(*args, kwargs)

File "/proj/env/lib/python3.8/site-packages/django/core/management/commands/migrate.py", line 243, in handle

post_migrate_state = executor.migrate(

File "/proj/env/lib/python3.8/site-packages/django/db/migrations/executor.py", line 117, in migrate

state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)

File "/proj/env/lib/python3.8/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards

state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)

File "/proj/env/lib/python3.8/site-packages/django/db/migrations/executor.py", line 227, in apply_migration

state = migration.apply(state, schema_editor)

File "/proj/env/lib/python3.8/site-packages/django/db/migrations/migration.py", line 124, in apply

operation.database_forwards(self.app_label, schema_editor, old_state, project_state)

File "/proj/env/lib/python3.8/site-packages/django/db/migrations/operations/models.py", line 92, in database_forwards

schema_editor.create_model(model)

File "/proj/env/lib/python3.8/site-packages/django/db/backends/base/schema.py", line 322, in create_model

sql, params = self.table_sql(model)

File "/proj/env/lib/python3.8/site-packages/django/db/backends/base/schema.py", line 195, in table_sql

'table': self.quote_name(model._meta.db_table),

File "/proj/env/lib/python3.8/site-packages/django/db/backends/base/schema.py", line 145, in quote_name

return self.connection.ops.quote_name(name)

File "/proj/env/lib/python3.8/site-packages/django/db/backends/mysql/operations.py", line 176, in quote_name

if name.startswith("") and name.endswith(""):

AttributeError: 'tuple' object has no attribute 'startswith'

The following error will be reported as soon as the new environment is submitted (migrate). Please solve it, thank you very much!

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

Last modified 4 years ago Last modified on 09/20/2016 12:24:13 PM
Back to Top