Trac Ticket Queries
Table of Contents
In addition to reports, Trac provides support for custom ticket queries, used to display lists of tickets meeting a specified set of 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 and no name/email 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 of 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.
Once you've edited your filters click the Update button to refresh your results.
Navigating Tickets
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.
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:
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:
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:
No results
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:
No results
Finally, if you wish to receive only the number of defects that match the query, use the count parameter.
[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
This is displayed as:
0
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 226)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #504 | invalid | The procedure entry point ?PyWinObject_AsHANDLE_object@@PAPAXH@Z could not be located in the dynamic link library pywintypes25.dll | htgoebel | jnhea@swbell.net |
| #499 | duplicate | PySide + phonon | htgoebel | pyinstaller.slowcoach@spamgourmet.com |
| #493 | invalid | IOError: [Errno 22] invalid mode ('rb') or filename: 'F:\\python\\12306\\dist\\t rain.exe?225280\\selenium\\webdriver\\firefox\\webdriver.xpi' | htgoebel | nmweizi@gmail.com |
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 226)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #504 | invalid | The procedure entry point ?PyWinObject_AsHANDLE_object@@PAPAXH@Z could not be located in the dynamic link library pywintypes25.dll | htgoebel | jnhea@swbell.net |
| Description |
This message has suddenly appeared when I build a ".exe" file of my python25 program on Vista. It also appears when I run the executable; but, if I just click the OK in the message box, the program appears to run ok. If I knew what caused the message (why it wants that "entry point") I might be able to find the problem, if there is one, in my program. Do you have any ideas? jnh |
|||
| #499 | duplicate | PySide + phonon | htgoebel | pyinstaller.slowcoach@spamgourmet.com |
| Description |
Hi. I'm on Windows XP, latest git PyInstaller?, using Python 2.6, PySide? 1.0.7. When I run pyinstaller, it all goes fine until I run the executable at which point I get the following output, the last 3 lines of which are repeated every time some audio is played: WARNING: bool __thiscall Phonon::FactoryPrivate::createBackend(void) phonon backend plugin could not be loaded WARNING: bool __thiscall Phonon::FactoryPrivate::createBackend(void) phonon backend plugin could not be loaded WARNING: bool __thiscall Phonon::FactoryPrivate::createBackend(void) phonon backend plugin could not be loaded WARNING: bool __thiscall Phonon::FactoryPrivate::createBackend(void) phonon backend plugin could not be loaded WARNING: Phonon::createPath: Cannot connect MediaObject ( no objectName ) to AudioOutput ( no objectName ). WARNING: bool __thiscall Phonon::FactoryPrivate::createBackend(void) phonon backend plugin could not be loaded WARNING: bool __thiscall Phonon::FactoryPrivate::createBackend(void) phonon backend plugin could not be loaded WARNING: bool __thiscall Phonon::FactoryPrivate::createBackend(void) phonon backend plugin could not be loaded This is a --onedir build, but I see there's nothing resembling pyside's `plugins/phonon_backend' in the resulting dist folder. All source (it's not a big application) is on github. (Otherwise, all working nicely, thanks!) Cheers for any help, Dave. |
|||
| #493 | invalid | IOError: [Errno 22] invalid mode ('rb') or filename: 'F:\\python\\12306\\dist\\t rain.exe?225280\\selenium\\webdriver\\firefox\\webdriver.xpi' | htgoebel | nmweizi@gmail.com |
| Description |
error info: F:\python\12306\dist\train>train
Traceback (most recent call last):
File "<string>", line 81, in <module>
File "<string>", line 14, in main
File "F:\python\12306\build\pyi.win32\train\outPYZ1.pyz\bb", line 50, in __init__
File "F:\python\12306\build\pyi.win32\train\outPYZ1.pyz\selenium.webdriver.firefox.webdriver", line 45, in __init__
File "F:\python\12306\build\pyi.win32\train\outPYZ1.pyz\selenium.webdriver.firefox.extension_connection", line 44, in __init__
File "F:\python\12306\build\pyi.win32\train\outPYZ1.pyz\selenium.webdriver.firefox.firefox_profile", line 124, in add_extension
File "F:\python\12306\build\pyi.win32\train\outPYZ1.pyz\selenium.webdriver.firefox.firefox_profile", line 225, in _install_extension
File "F:\python\12306\build\pyi.win32\train\outPYZ1.pyz\zipfile", line 683, in __init__
IOError: [Errno 22] invalid mode ('rb') or filename: 'F:\\python\\12306\\dist\\train\\train.exe?192512\\selenium\\webdriver\\firefox\\webdriver.xpi'
WEBDRIVER_EXT = "webdriver.xpi"
webdriver.xpi and firefox_profile.py
E:\Python26\Lib\site-packages\selenium-2.16.0-py2.6.egg\selenium\webdriver\firefox 2012/01/14 08:35 <DIR> .
2012/01/14 08:35 <DIR> ..
2012/01/14 08:35 <DIR> amd64
2012/01/14 08:35 2,561 extension_connection.py
2012/01/14 08:35 3,482 extension_connection.pyc
2012/01/14 08:35 5,982 firefox_binary.py
2012/01/14 08:35 6,921 firefox_binary.pyc
2012/01/14 08:35 9,358 firefox_profile.py
2012/01/14 08:35 10,555 firefox_profile.pyc
2012/01/14 08:35 2,962 webdriver.py
2012/01/14 08:35 3,426 webdriver.pyc
2012/01/14 08:35 2,842,199 webdriver.xpi
2012/01/14 08:35 <DIR> x86
2012/01/14 08:35 613 __init__.py
2012/01/14 08:35 181 __init__.pyc
11 files 2,888,240 bytes
train.spec # -*- mode: python -*-
a = Analysis([os.path.join(HOMEPATH,'support\\_mountzlib.py'), os.path.join(CONFIGDIR,'support\\useUnicode.py'), 'train.py'],
pathex=['F:\\python\\12306'],
hookspath=None)
pyz = PYZ(a.pure)
exe = EXE(pyz,
a.scripts,
exclude_binaries=1,
name=os.path.join('build\\pyi.win32\\train', 'train.exe'),
debug=False,
strip=None,
upx=True,
console=True )
a.datas += [(r'selenium\\webdriver\\firefox\\webdriver.xpi',r'E:\Python26\Lib\site-packages\selenium-2.16.0-py2.6.egg\selenium\webdriver\firefox\webdriver.xpi','data'),]
coll = COLLECT( exe,
a.binaries,
a.zipfiles,
a.datas,
strip=None,
upx=True,
name=os.path.join('dist', 'train'))
|
|||
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 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 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 |
See also: TracTickets, TracReports, TracGuide
