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.
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.
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:
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
[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
Which 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 in by placing pipes (
|) between the columns:
This is displayed as:
Results (1 - 3 of 25790)
In table format you can also have full rows by using rows=<field>:
This is displayed as:
Results (1 - 3 of 25790)
|#27750||needsinfo||TypeError when running manage.py migrate|
Is returning this error when I try to run ./manage.py migrate in a model:
class Cast(models.Model): movie = models.ForeignKey("movies.Movie") artist = models.ForeignKey("artists.Artist", db_column="actor_id")
migrations.AlterField( model_name='cast', name='artist', field=models.ForeignKey(db_column='actor_id', on_delete=django.db.models.deletion.CASCADE, to='artists.Artist'), ),
Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python3.5/site-packages/django/core/management/__init__.py", line 353, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.5/site-packages/django/core/management/__init__.py", line 345, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 348, in run_from_argv self.execute(*args, **cmd_options) File "/usr/local/lib/python3.5/site-packages/raven/contrib/django/management/__init__.py", line 41, in new_execute return original_func(self, *args, **kwargs) File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 399, in execute output = self.handle(*args, **options) File "/usr/local/lib/python3.5/site-packages/django/core/management/commands/migrate.py", line 200, in handle executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial) File "/usr/local/lib/python3.5/site-packages/django/db/migrations/executor.py", line 92, in migrate self._migrate_all_forwards(plan, full_plan, fake=fake, fake_initial=fake_initial) File "/usr/local/lib/python3.5/site-packages/django/db/migrations/executor.py", line 121, in _migrate_all_forwards state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial) File "/usr/local/lib/python3.5/site-packages/django/db/migrations/executor.py", line 198, in apply_migration state = migration.apply(state, schema_editor) File "/usr/local/lib/python3.5/site-packages/django/db/migrations/migration.py", line 123, in apply operation.database_forwards(self.app_label, schema_editor, old_state, project_state) File "/usr/local/lib/python3.5/site-packages/django/db/migrations/operations/fields.py", line 201, in database_forwards schema_editor.alter_field(from_model, from_field, to_field) File "/usr/local/lib/python3.5/site-packages/django/db/backends/base/schema.py", line 482, in alter_field old_db_params, new_db_params, strict) File "/usr/local/lib/python3.5/site-packages/django/db/backends/postgresql/schema.py", line 110, in _alter_field new_db_params, strict, File "/usr/local/lib/python3.5/site-packages/django/db/backends/base/schema.py", line 545, in _alter_field self.execute(self._rename_field_sql(model._meta.db_table, old_field, new_field, new_type)) File "/usr/local/lib/python3.5/site-packages/django/db/backends/base/schema.py", line 867, in _rename_field_sql "old_column": self.quote_name(old_field.column), File "/usr/local/lib/python3.5/site-packages/django/db/backends/base/schema.py", line 113, in quote_name return self.connection.ops.quote_name(name) File "/usr/local/lib/python3.5/site-packages/django/db/backends/postgresql/operations.py", line 95, in quote_name if name.startswith('"') and name.endswith('"'): TypeError: startswith first arg must be bytes or a tuple of bytes, not str
The error is in the field
Detail: I didn't changed anything in this fields, it's because when I migrated from Python 2.7.5 to Python 3.5 the verbose_name changed (removed the u"") and asked to generate new migrations. I think it is unnecessary.
|#27744||duplicate||Complex prefetch_related broken (from 1.9 to 1.10)|
Was working on : 1.9.10 Is not working on : 1.10.5
from offer.models import Price, PriceGrid from django.db.models import Prefetch price_queryset = Price.objects.prefetch_related('calculation_rules__rule') pricegrids = PriceGrid.objects.all() pricegrids = pricegrids.prefetch_related(Prefetch('prices', queryset=price_queryset)) for pg in pricegrids: print(pg.pk)
But this still works :
pgs = PriceGrid.objects.prefetch_related('prices__calculation_rules__rule').all() for pg in pgs: for price in pg.prices.all(): for dr in price.calculation_rules.all(): print(dr.rule.pk)
Models (extracts) :
class Price(models.Model): grid = models.ForeignKey(PriceGrid, related_name="prices") class PriceCalculationRule(models.Model): price = models.ForeignKey(Price, on_delete=models.CASCADE, related_name="calculation_rules") rule = models.ForeignKey(Rule, on_delete=models.PROTECT, verbose_name="Condition")
|#27740||wontfix||Allow content_type or object_id of GenericForeignKey to be field on related model|
I would like to specify a related model field as the values of content_type or object_id of GenericForeignKey. For example:
class Widget(models.Model): content_type = models.ForeignKey(ContentType, on_delete=models.CASCADE) class Gadget(models.Model): widget = models.ForeignKey(Widget, on_delete=models.CASCADE) object_id = models.PositiveIntegerField() content_object = GenericForeignKey('widget__content_type', 'object_id')
If I tried to use this now, I would get the error:
Traceback (most recent call last): File "django/db/models/options.py", line 617, in get_field return self.fields_map[field_name] KeyError: 'widget__content_type' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "django/contrib/contenttypes/fields.py", line 224, in __get__ f = self.model._meta.get_field(self.ct_field) File "django/db/models/options.py", line 619, in get_field raise FieldDoesNotExist('%s has no field named %r' % (self.object_name, field_name)) django.core.exceptions.FieldDoesNotExist: Gadget has no field named 'widget__content_type'
One use case for this is a generic custom attribute system, where attribute fields can be created for any other model. The "fields" model has the content_type field. The "values" model has the object ID and value fields. The developer would like to query the object that the "values" record references: value.content_object
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
| 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
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.
| ||query tickets created in 2007|
| ||query tickets created during the previous month|
| ||query tickets that have been modified in the last week|
| ||query tickets that have been inactive for the last 30 days|