Edgewall Software

Version 1 (modified by Steffen Hoffmann, 11 years ago) ( diff )

1st part of initial German translation based on /TracQuery@29

Trac-Ticket-Abfragen

Andere Sprachen:

Zusätzlich zu Berichten bietet Trac benutzerdefinierte Ticketabfragen an, die zum Auflisten von Tickets entspechend angegebener Kriterien verwendet werden.

Um eine benutzerdefinierte Abfrage vorzubreiten und auszuführen, wechseln Sie in der Navigationsleiste zu Tickets anzeigen und wählen den Verweis Individuelle Abfrage.

Filter

Wenn Sie die Abfrageseite das erste Mal besuchen, wird Ihnen der Standard-Filter Sie betreffende Tickets anzeigen:

  • Falls Sie angemeldet sind, dann werden alle offenen Tickets, die angezeigt werden, Ihnen zugewiesene Tickets öffnen.
  • Falls Sie nicht angemeldet sind, jedoch einen Namen oder eine E-Mail-Adresse in den Benutzer-Einstellungen angegeben haben, dann werden Ihnen alle offenen Tickets angezeigt, deren Kopie-Liste Ihre E-Mail-Adresse (oder, bei fehlender E-Mail-Adresse, Ihren Namen) enthält.
  • Ohne Anmeldung und ohne Angaben zu Name und E-Mail-Adresse in den Benutzer-Einstellungen werden alle offenen Vorgänge angezeigt.

Vorhandene Filter können durch Anklicken der Minus-Schaltfläche links daneben entfernt werden. Aus den Auswahllisten am Ende des Filterkastens ('UND'-Bedingungen links, 'ODER'-Bedingungen rechts) lassen sich neue Filter hinzufügen. Filter mit Eingabefeld oder Auswahlliste der Optionen können mehrfach hinzugefügt werden, um diese Kriterien mit oder zu verknüpfen.

Sie können die Felder direkt unterhalb des Filterkastens nutzen, um die Ergebnisse nach einem Feld zu gruppieren oder die vollständige Beschreibung zu jedem Ticket anzuzeigen.

Nachdem Sie Ihre Filter bearbeitet haben, klicken Sie die Schaltfläche Aktualisieren zum Anpassen Ihrer Ergebnisse.

Ein Klick auf eines der Abfrageergebnisse bringt Sie zu diesem Ticket. Sie können sich durch die Ergebnisse bewegen, indem Sie die Verweise nächstes Ticket oder vorheriges Ticket direkt unterhalb der Hauptnavigationsleiste anklicken, oder Sie wählen den Verweis Zurück zur Abfrage um zur Abfrageseite zurückzukehren.

Sie können ruhig jedes der Tickets bearbeiten und nach dem Abspeichern Ihrer Änderungen den Durchgang durch die Ergebnisse mit den Verweisen !nächstes/vorheriges/Zurück zur Abfrage fortsetzen. Wenn Sie zur Abfrage zurückkehren, werden alle bearbeiteten Tickets mit kursivem Text dargestellt. Falls eines der Tickets so verändert wurde, dass es den Abfragekriterien nicht mehr entspricht , dann wird der Text grau. Schließlich wird ein neues Ticket, das den Abfragekriterien entspricht, fett dargestellt.

Durch nochmaliges Anklicken der Schaltfläche Aktualisieren können die Abfrageergebnisse wiederum angepaßt und diese Statuskennzeichen gelöscht werden.

Abfragen speichern

Trac bietet Ihnen an, die Abfrage als benannte Abfrage abzuspeichern, die vom Bericht-Modul aus erreichbar ist. Um eine Abfrage zu speichern, stellen Sie sicher, dass die Ansicht Aktualisiert haben, und klicken Sie dann die Schaltfläche Abfrage speichern, die unterhalb der Ergebnisse angezeigt wird. Sie können Verweise auf Abfragen auch wie nachfolgend beschrieben in Wiki-Text ablegen.

Anmerkung: Eine Art, Abfragen wie die folgenden einfach aufzubauen, ist die, Abfragen im Modul für benutzerdefinierte Berichte zu erstellen, zu testen und nach Fertigstellung Abfrage speichern zu klicken. Dies baut den Abfrageausdruck für Sie auf. Sie müssen nur noch überflüssige Zeilenumbrüche entfernen.

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:

#181
Wiki preview injects new lines
#204
request for colour legend (or something similar) for ticket groups in reports
#226
Ticket Dependencies
#239
Link to diff of specifik wiki change instead of the page itself
#351
All ticket modifications should be tracked in timeline
#413
Installing on Windows, drive other than C:
#450
Diffviewer should try to convert the text into utf-8.
#475
merging of similar tickets
#519
Python process sometimes hangs on Windows Server 2003
#529
IE 5-6 over HTTPS broken downloads

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.

A more compact representation without the ticket summaries is also available:

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

This is displayed as:

#181, #204, #226, #239, #351, #413, #450, #475, #519, #529

Finally if you wish to receive only the number of defects that match the query using the count parameter.

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

This is displayed as:

10

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#13481 fixed Tigris.org no longer supported: affects svn interwiki link figaro
Description

Subversion hosting has been migrated from tigris.org to apache.org: https://subversion.apache.org/ However, both InterWiki and InterMapTxt mention the support for the format where the former site is still used. On t.e.o. the amount of occurrences is small: 3 occurrences with the most recent one from 2014.

Hence:

  • Trac administrators need to decide whether to backport to older tickets via apache.org, for example the issue with id 4526 to resolve to https://issues.apache.org/jira/browse/SVN-4526?issueNumber=4526
  • As the Trac development community we need to decide whether to support/change the url for full compatibility or drop support for older tickets.
#13479 fixed make extraction fails with TypeError Jun Omae Ryan J Ollos
Description
$ make status

Python: /Users/rjollos/.pyenv/shims/python

/Users/rjollos/.pyenv/versions/trac-py310/lib/python3.10/site-packages/_distutils_hack/__init__.py:30: UserWarning: Setuptools is replacing distutils.
  warnings.warn("Setuptools is replacing distutils.")
  Package        Version
  --------------------------------------------------------------------------------------
  Python       : 3.10.3 (main, Mar 22 2022, 21:01:41) [Clang 13.1.6 (clang-1316.0.21.2)]
  Setuptools   : 62.1.0
  Pip          : 22.0.4
  Wheel        : 0.37.1
  Jinja2       : 3.0.3
  Babel        : 2.9.1
  sqlite3      : 2.6.0 (3.36.0)
  PySqlite3    : not installed
  PyMySQL      : 1.0.2
  Psycopg2     : 2.9.3 (dt dec pq3 ext lo64)
  SVN bindings : 1.15.0 (under development)
  Mercurial    : 6.1
  Pygments     : 2.11.2
  Textile      : 4.0.2
  Pytz         : 2022.1
  Docutils     : 0.17.1
  Selenium     : 4.1.3
  PyTidyLib    : 0.3.2 (5.8.0 /usr/local/lib/libtidy.dylib)
  LXML         : 4.8.0
  coverage     : 6.3.2

Variables:
  PATH=/Users/rjollos/Documents/Workspace/trac-dev/bin:/Users/rjollos/Documents/Workspace/trac-dev/subversion-trunk/local/bin:/usr/local/Cellar/tidy-html5/5.6.0/bin:/Users/rjollos/.pyenv/shims:/usr/local/opt/sqlite/bin:/usr/local/opt/gnu-sed/libexec/gnubin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/VMware Fusion.app/Contents/Public:/Library/TeX/texbin:/usr/local/munki:/opt/X11/bin:/Library/Apple/usr/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Applications/Wireshark.app/Contents/MacOS:/Users/rjollos/.pyenv/bin
  PYTHONPATH=.
  TRAC_TEST_DB_URI=
  server-options= -p 8000 -a '*,/Users/rjollos/Documents/Workspace/trac-dev/tracenvs/htdigest.trac,trac' -r -e /Users/rjollos/Documents/Workspace/trac-dev/tracenvs

External dependencies:
  Git version: git version 2.35.1
  Subversion version: 1.15.0-dev
$ make extraction
python  setup.py  extract_messages  extract_messages_js  extract_messages_tracini
running extract_messages
extracting messages from tracopt/__init__.py
extracting messages from tracopt/perm/__init__.py
extracting messages from tracopt/perm/authz_policy.py
Traceback (most recent call last):
  File "/Users/rjollos/Documents/Workspace/trac-dev/teo-rjollos.git/setup.py", line 42, in <module>
    setup(**extra)
  File "/Users/rjollos/.pyenv/versions/trac-py310/lib/python3.10/site-packages/setuptools/__init__.py", line 87, in setup
    return distutils.core.setup(**attrs)
  File "/Users/rjollos/.pyenv/versions/trac-py310/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 148, in setup
    return run_commands(dist)
  File "/Users/rjollos/.pyenv/versions/trac-py310/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 163, in run_commands
    dist.run_commands()
  File "/Users/rjollos/.pyenv/versions/trac-py310/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 967, in run_commands
    self.run_command(cmd)
  File "/Users/rjollos/.pyenv/versions/trac-py310/lib/python3.10/site-packages/setuptools/dist.py", line 1214, in run_command
    super().run_command(command)
  File "/Users/rjollos/.pyenv/versions/trac-py310/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 986, in run_command
    cmd_obj.run()
  File "/Users/rjollos/.pyenv/versions/trac-py310/lib/python3.10/site-packages/babel/messages/frontend.py", line 481, in run
    for filename, lineno, message, comments, context in extracted:
  File "/Users/rjollos/.pyenv/versions/trac-py310/lib/python3.10/site-packages/babel/messages/extract.py", line 149, in extract_from_dir
    for message_tuple in check_and_call_extract_file(
  File "/Users/rjollos/.pyenv/versions/trac-py310/lib/python3.10/site-packages/babel/messages/extract.py", line 207, in check_and_call_extract_file
    for message_tuple in extract_from_file(
  File "/Users/rjollos/.pyenv/versions/trac-py310/lib/python3.10/site-packages/babel/messages/extract.py", line 243, in extract_from_file
    return list(extract(method, fileobj, keywords, comment_tags,
  File "/Users/rjollos/.pyenv/versions/trac-py310/lib/python3.10/site-packages/babel/messages/extract.py", line 325, in extract
    for lineno, funcname, messages, comments in results:
  File "/Users/rjollos/Documents/Workspace/trac-dev/teo-rjollos.git/trac/dist.py", line 148, in extract_python
    for _ in tokens:
  File "/Users/rjollos/.pyenv/versions/3.10.3/lib/python3.10/tokenize.py", line 498, in _tokenize
    if line[pos] in '#\r\n':           # skip comments or blank lines
TypeError: 'in <string>' requires string as left operand, not int
make: *** [extraction] Error 1
#13477 fixed ImportError: cannot import name 'contextfilter' from 'jinja2' Jun Omae Ryan J Ollos
Description
$ pip list | grep Jinja
Jinja2                        3.1.1
Traceback (most recent call last):
  File "/Users/rjollos/Documents/Workspace/trac-dev/teo-rjollos.git/contrib/checkwiki.py", line 22, in <module>
    from trac.test import EnvironmentStub, Mock, MockPerm
  File "/Users/rjollos/Documents/Workspace/trac-dev/teo-rjollos.git/trac/test.py", line 47, in <module>
    from trac.env import Environment
  File "/Users/rjollos/Documents/Workspace/trac-dev/teo-rjollos.git/trac/env.py", line 52, in <module>
    from trac.web.chrome import Chrome
  File "/Users/rjollos/Documents/Workspace/trac-dev/teo-rjollos.git/trac/web/chrome.py", line 40, in <module>
    from trac.mimeview.api import RenderingContext, get_mimetype
  File "/Users/rjollos/Documents/Workspace/trac-dev/teo-rjollos.git/trac/mimeview/__init__.py", line 14, in <module>
    from trac.mimeview.api import *
  File "/Users/rjollos/Documents/Workspace/trac-dev/teo-rjollos.git/trac/mimeview/api.py", line 70, in <module>
    from trac.resource import Resource
  File "/Users/rjollos/Documents/Workspace/trac-dev/teo-rjollos.git/trac/resource.py", line 21, in <module>
    from trac.util.presentation import classes
  File "/Users/rjollos/Documents/Workspace/trac-dev/teo-rjollos.git/trac/util/presentation.py", line 24, in <module>
    from jinja2 import Undefined, contextfilter, evalcontextfilter
ImportError: cannot import name 'contextfilter' from 'jinja2' (/Users/rjollos/.pyenv/versions/trac-py310/lib/python3.10/site-packages/jinja2/__init__.py)
make: *** [update-help] Error 1
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 litteral & 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

Leseempfehlungen: TracTickets, TracReports, TracGuide

Note: See TracWiki for help on using the wiki.