Context Navigation

+1
← Previous Version
View Latest Version
Next Version →

Version 1 (modified by Steffen Hoffmann, 13 years ago) ( diff )
1st part of initial German translation based on /TracQuery@29

Trac-Ticket-Abfragen

Andere Sprachen:

Deutsch
English
@29 - @62

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.

Tickets durchgehen

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.

Using TracLinks

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:

Results (1 - 3 of 11268)

1 2 3 4 5 6 7 8 9 10 11 →


Ticket	Resolution	Summary	Owner	Reporter
#13748	duplicate	Time to use `build` from `setuptools` instead of `distutils`?		anonymous
#13747	fixed	IndexError raised from GitRepository.normalize_rev('FFFF') if the repository has 5000+ revisions	Jun Omae	Jun Omae
#13744	fixed	[PATCH] SpamFilter: Support pillow 10 for ImageCaptcha	Dirk Stöcker	niels.reedijk@…

1 2 3 4 5 6 7 8 9 10 11 →

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

1 2 3 4 5 6 7 8 9 10 11 →

Ticket

Resolution

Summary

Owner

Reporter

#13748 duplicate Time to use `build` from `setuptools` instead of `distutils`? anonymous

Description

The following feature in setuptools has been deprecated for almost 2 years and is about to be removed:

https://github.com/pypa/setuptools/blob/1ed759173983656734c3606e9c97a348895e5e0c/setuptools/command/build.py#L13-L27

It might be a good idea to import build directly from setuptools for the following code:

https://github.com/edgewall/trac/blob/8fb2bf0e5ab885fb4e174d11599e6bc76bf71b8a/trac/dist.py#L558-L559

(build is available directly from setuptools, starting on version v62.4.0)

#13747 fixed IndexError raised from GitRepository.normalize_rev('FFFF') if the repository has 5000+ revisions Jun Omae Jun Omae

Description

Traceback (most recent call last):
  File "/venv/lib/python2.7/site-packages/trac/timeline/web_ui.py", line 198, in process_request
    filters) or []:
  File "/venv/lib/python2.7/site-packages/trac/versioncontrol/web_ui/changeset.py", line 917, in get_timeline_events
    for event in generate_changesets(repos):
  File "/venv/lib/python2.7/site-packages/trac/versioncontrol/web_ui/changeset.py", line 892, in generate_changesets
    for cset in changesets:
  File "/venv/lib/python2.7/site-packages/tracopt/versioncontrol/git/git_fs.py", line 72, in get_changesets
    csets = list(csets)
  File "/venv/lib/python2.7/site-packages/trac/versioncontrol/cache.py", line 82, in get_changesets
    yield self.get_changeset(rev)
  File "/venv/lib/python2.7/site-packages/tracopt/versioncontrol/git/git_fs.py", line 85, in get_changeset
    return GitCachedChangeset(self, self.normalize_rev(rev), self.env)
  File "/venv/lib/python2.7/site-packages/tracopt/versioncontrol/git/git_fs.py", line 56, in normalize_rev
    normrev = self.repos.git.verifyrev(rev)
  File "/venv/lib/python2.7/site-packages/tracopt/versioncontrol/git/PyGIT.py", line 710, in verifyrev
    fullrev = self.fullrev(rev)
  File "/venv/lib/python2.7/site-packages/tracopt/versioncontrol/git/PyGIT.py", line 780, in fullrev
    srevs = _rev_cache.srev_dict[self.__rev_key(srev)]
IndexError: list index out of range

git-data.sh

#! /bin/sh
n="$1"
echo 'blob'
echo 'mark :1'
echo 'data 0'
echo
echo 'reset refs/heads/master'
for i in $(seq 1 "$n"); do
    ts=$((999999999 + $i))
    echo 'commit refs/heads/master'
    echo 'mark :2'
    echo "author Joe <joe@example.com> $ts +0000"
    echo "committer Joe <joe@example.com> $ts +0000"
    echo 'data 2'
    echo '.'
    echo 'M 100644 :1 .gitignore'
    echo
done

Creating test repository with 5,500 revisions

$ git init --bare /dev/shm/git-repos
$ /dev/shm/git-data.sh 5500 | git --git-dir /dev/shm/git-repos fast-import
$ git --git-dir /dev/shm/git-repos rev-list --all | wc -l
5500
$ git --git-dir /dev/shm/git-repos rev-list --all | sed -e 's/^\(....\).*/\1/' | sort -u | wc -l
5272
$ git --git-dir /dev/shm/git-repos rev-list --all | sed -e 's/^\(....\).*/\1/' | sort -u | tail -1
fff9

Trying `GitRepository.normalize_rev('FFFF')`

$ (cd / && ~/venv/trac/1.6/bin/python)
Python 3.11.9 (main, Apr  6 2024, 17:59:24) [GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from trac.test import EnvironmentStub
>>> from tracopt.versioncontrol.git.git_fs import GitConnector
>>> env = EnvironmentStub()
>>> connector = GitConnector(env)
>>> repos = connector.get_repository('git', '/dev/shm/git-repos', {'id': 42, 'name': ''})
>>> repos.git.rev_cache
RevCache(youngest_rev=b'39f74414152cc0645367502e8d05a83e34f9c084', oldest_rev=b'86989f7deb1be18dcb970f221d017c58417c56a2', rev_dict=5500 entries, refs_dict=2 entries, srev_dict=65530 entries)
>>> type(repos.git.rev_cache.srev_dict)
<class 'list'>
>>> repos.normalize_rev('FFFF')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/jun66j5/venv/trac/1.6/lib/python3.11/site-packages/tracopt/versioncontrol/git/git_fs.py", line 569, in normalize_rev
    normrev = self.git.verifyrev(rev)
              ^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/jun66j5/venv/trac/1.6/lib/python3.11/site-packages/tracopt/versioncontrol/git/PyGIT.py", line 796, in verifyrev
    result = get_verifyrev(self._fs_from_unicode(rev))
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/jun66j5/venv/trac/1.6/lib/python3.11/site-packages/tracopt/versioncontrol/git/PyGIT.py", line 771, in get_verifyrev
    fullrev = self.fullrev(rev)
              ^^^^^^^^^^^^^^^^^
  File "/home/jun66j5/venv/trac/1.6/lib/python3.11/site-packages/tracopt/versioncontrol/git/PyGIT.py", line 847, in fullrev
    srevs = _rev_cache.srev_dict[self.__rev_key(rev)]
            ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
IndexError: list index out of range
>>> repos.normalize_rev('FFF9')
'fff9a43563e57b091ed4a44ffa3e244082f51175'
>>> repos.git.rev_cache.srev_dict[0xFFF9]
(b'fff9a43563e57b091ed4a44ffa3e244082f51175',)

Patch

tracopt/versioncontrol/git/PyGIT.py

diff --git a/tracopt/versioncontrol/git/PyGIT.py b/tracopt/versioncontrol/git/PyGIT.py
index e1e660b19..62f0a4bf0 100644

                class Storage(object):
         try:
             srevs = _rev_cache.srev_dict[self.__rev_key(rev)]
         except KeyError:
+        except (KeyError, IndexError):
             return None
         resolved = None

#13744 fixed [PATCH] SpamFilter: Support pillow 10 for ImageCaptcha Dirk Stöcker niels.reedijk@…

Description

Currently the ImageCaptcha component is not compatible with a modern pillow, due to API changes. This patch makes it compatible with Pillow 10 (tested with 10.2.0) and bumps the minimum required version.

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.

Download in other formats:

Plain Text

Context Navigation

Trac-Ticket-Abfragen

Table of Contents

Andere Sprachen:

Filter

Tickets durchgehen

Abfragen speichern

Using TracLinks

Using the [[TicketQuery]] Macro

Customizing the table format

Results (1 - 3 of 11268)

Full rows

Results (1 - 3 of 11268)

git-data.sh

Creating test repository with 5,500 revisions

Trying GitRepository.normalize_rev('FFFF')

Patch

tracopt/versioncontrol/git/PyGIT.py

Query Language

Download in other formats:

Using the `[[TicketQuery]]` Macro

Trying `GitRepository.normalize_rev('FFFF')`