![[Chimera Issue Tracking System]](/trac/chimera/chrome/site/chimera_logo.png){kind=logo}
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.
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.
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.
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.
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:
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:
Results (1 - 3 of 20312)
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 20312)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #27121 | duplicate | AlphaFold3 mmCIF omits chain description | ||
| Description |
The following bug report has been submitted:
Platform: Windows64 (WGL) Microsoft Windows Unknown 10.0 (Build 26200) x64
Chimera Version: 1.15_b42258
Description
(Describe the actions that caused this problem to occur here)
Open models
#0 mFCER1_MAR1Fab_J367_011_volume_map_244k_3.57A.mrc
#1 mFCER1_MAR1Fab_J367_011_volume_map_sharp_244k_3.57A.mrc
#2 fold_2026_06_26_14_11_mar1_revised_model_0.cif
Reply log:
[MMLIB:WARNING] read_struct_conn: struct_conn table not found
Traceback (most recent call last):
File "C:\Program Files\Chimera 1.15\share\chimera\triggerSet.py", line 83, in invoke
self._funcData, triggerData)
File "C:\Program Files\Chimera 1.15\share\chimera\__init__.py", line 2664, in categorizeSurface
processNewMolecules(prefModels)
File "C:\Program Files\Chimera 1.15\share\chimera\__init__.py", line 2637, in processNewMolecules
preset(openedModels=smartMols)
File "C:\Program Files\Chimera 1.15\share\chimera\preset.py", line 271, in preset
for seq in m.sequences():
File "C:\Program Files\Chimera 1.15\share\chimera\Sequence.py", line 993, in getSequences
description = entity[index]['pdbx_description']
KeyError: 'pdbx_description'
Error processing trigger "Bond":
KeyError: 'pdbx_description'
File "C:\Program Files\Chimera 1.15\share\chimera\Sequence.py", line 993, in getSequences
description = entity[index]['pdbx_description']
See reply log for Python traceback.
Model 2 (fold_2026_06_26_14_11_mar1_revised_model_0.cif) appears to be a protein without secondary structure assignments.
Automatically computing assignments using 'ksdssp' and parameter values:
energy cutoff -0.5
minimum helix length 3
minimum strand length 3
Use command 'help ksdssp' for more information.
Traceback (most recent call last):
File "C:\Program Files\Chimera 1.15\share\chimera\triggerSet.py", line 83, in invoke
self._funcData, triggerData)
File "C:\Program Files\Chimera 1.15\share\chimera\__init__.py", line 2664, in categorizeSurface
processNewMolecules(prefModels)
File "C:\Program Files\Chimera 1.15\share\chimera\__init__.py", line 2637, in processNewMolecules
preset(openedModels=smartMols)
File "C:\Program Files\Chimera 1.15\share\chimera\preset.py", line 271, in preset
for seq in m.sequences():
File "C:\Program Files\Chimera 1.15\share\chimera\Sequence.py", line 993, in getSequences
description = entity[index]['pdbx_description']
KeyError: 'pdbx_description'
――――――――――――――――――――
OpenGL Vendor: Intel
OpenGL Renderer: Intel(R) UHD Graphics 630
OpenGL Version: 4.6.0 - Build 30.0.100.9864
Manufacturer: Dell Inc.
Model: OptiPlex 7060
TotalPhysicalMemory: 34146140160
――――――――――――――――――――
Multisampling: False
Shadows: False
Shadow texture size: 2048
Silhouettes: False
Depth cue: True
Subdivision quality: 1.50
Single-layer transparency: True
Transparent background: False
Shaders supported: True
Using shader: True
Window size: 1352 807
Camera mode: mono
Orthographic projection: False
Center of rotation: front center
Near/far clipping: False
Key light: True
Fill light: True
Back light: False
Ambient light: 0.20
Specular sharpness: 30.00
Specular reflectivity: 1.00
――――――――――――――――――――
AntialiasLines: native
AntialiasPoints: native
BlendEquation: native
BlendFuncSeparate: native
BrokenAttribLocation: native, disabled
ChoosePixelFormat: extension
ColorTable: not supported
CompileAndExecute: native
CompiledVertexArray: extension
CubeMap: native
CullVertex: not supported
DrawElementsInstanced: native, disabled
DrawRangeElements: native
FBConfig: not supported
FBOShadows: native
FastMultisampling: native, disabled
FramebufferMultisample: native
FramebufferObject: native
LimitVertexAttribDivisor: native, disabled
Multisample: native
Multitexture: native
PackedDepthStencil: native
PalettedTexture: not supported
PointParameters: native
SeamlessCubeMap: native
SeparateSpecularColor: native
Shading: native
Shadows: native
StereoMultisample: native
StereoRubberBanding: native
Texture3D: native
TextureColorTable: not supported
TextureEdgeClamp: native
TrustColorLogicBlend: native
TrustNormals: native
VertexArray: native
VertexAttrib: native
VertexAttribDivisor: native
VertexBufferObject: native
WindowPos: not supported
|
|||
| #27120 | not_a_bug | Proofpoint Essentials - Quarantine Digest | ||
| Description |
Proofpoint Essentials - Quarantine Digest
https://us5.proofpointessentials.com/app/digest.php?ts=1782345722&action=hp&a_id=4i4534021470f106ccd00b8ebf03e654336a91a9f76f1e6034fdca705ac77b8957c29717b0eeee126fd9d316183c0c722dbe141245c82f91e14475f81fe560d3070b
https://www.cgl.ucsf.edu
UCSF RBVI: https://us5.proofpointessentials.com/logo.php?e_uuid=4ia9743aa9fdfc32936100c89f6297d807383f63cdcab7feb403033576c033d0b175775ca5ef06e96430bad5c7176f5b8c1ac2ed57845c133ee32e62e18c9dca3b50f3c234888ac2b305f37ff3
Quarantine Digest
Sign in to your account: https://us5.proofpointessentials.com/app/login.php?ts=1782345722&e_uuid=4ia9743aa9fdfc32936100c89f6297d807383f63cdcab7feb403033576c033d0b175775ca5ef06e96430bad5c7176f5b8c1ac2ed57845c133ee32e62e18c9dca3b50f3c234888ac2b305f37ff3
chimera bugs
chimera-bugs@cgl.ucsf.edu
2026-06-24
17:02 PDT
----------------------------------------------------------------------------------------------
Quarantined (by Score)
----------------------------------------------------------------------------------------------
Address: "Accounting Voice Processing Completed|6/25/2026 12:24:02 a...., quickbooks@notification.intuit.com
Subject: Payment Acknowledgment-ACH Payment Successfully Processed
Delivery Date/Time: 24 Jun 26 - 15:24
Contact Administrator to take action on this email
https://us5.proofpointessentials.com/app/digest.php?ts=1782345722&action=hp&a_id=4i4534021470f106ccd00b8ebf03e654336a91a9f76f1e6034fdca705ac77b8957c29717b0eeee126fd9d316183c0c722dbe141245c82f91e14475f81fe560d3070b
Sign in to your account: https://us5.proofpointessentials.com/app/login.php?ts=1782345722&e_uuid=4ia9743aa9fdfc32936100c89f6297d807383f63cdcab7feb403033576c033d0b175775ca5ef06e96430bad5c7176f5b8c1ac2ed57845c133ee32e62e18c9dca3b50f3c234888ac2b305f37ff3
Request New Digest: https://us5.proofpointessentials.com/app/digest.php?action=request&k=k1&payload=4i469ef76e496c2dcebf8ba059cbffeff25480ed11fea498b5b1151c55a23d91e87fb5882c90d3db3c33127cf6a0d5eb27c1a44f50dfbc068e2b894ccfe2049df444e4e591e0154aa438eee232fa2fce2b55640c70a29e0617aea06e40bd45ebb263a638f806402b6288d179d050714179de44f36484d9460b9b56729f2d20d6f11512dca01355574fc385f3292f3b99f278f4b0d2b1c31b4316ee395498703c9b43d4067f9212251f2cc7a1d27ad56cb9bbf7c95fe2e3b88df3631569a34e62edf936a82dfcee57e627ed092ef05f381096f7266cd8cf0ba6be20c292355ef7f780cf1c25a00f0eb3fc8ab34e61c20801b76fd51eec0604a049483dd7cff17625dc87ad23d12722a773c91c3c94203d1e258a41&e_uuid=4ia9743aa9fdfc32936100c89f6297d807383f63cdcab7feb403033576c033d0b175775ca5ef06e96430bad5c7176f5b8c1ac2ed57845c133ee32e62e18c9dca3b50f3c234888ac2b305f37ff3&a_id=4i4534021470f106ccd00b8ebf03e654336a91a9f76f1e6034fdca705ac77b8957c29717b0eeee126fd9d316183c0c722dbe141245c82f91e14475f81fe560d3070b
https://www.proofpoint.com/us/products/essentials
© Proofpoint, Inc. 2004-2026All Rights Reserved
|
|||
| #27119 | not_a_bug | Proofpoint Essentials - Quarantine Digest | ||
| Description |
Proofpoint Essentials - Quarantine Digest
https://us5.proofpointessentials.com/app/digest.php?ts=1782331391&action=hp&a_id=4ibed484b6f0c72c25a423e1f45537cce236ec3fac05ca8caa5ca1907ca25a0e7ee00bf18d19d4153b4eb8b65b139e46ed18565e0b6d2b46e2ac9e86f317bc0a96ae
https://www.cgl.ucsf.edu
UCSF RBVI: https://us5.proofpointessentials.com/logo.php?e_uuid=4ibe1d017b4cb6e70b38cf3a6a2a76b3aff59a379040568108ef2624c502bdf7a28f2cff7f91483a3f6586ee8eb1c76ccd0b821646cbd1d65b09cda90dcad627824293ee00c2afd81276f1e625
Quarantine Digest
Sign in to your account: https://us5.proofpointessentials.com/app/login.php?ts=1782331391&e_uuid=4ibe1d017b4cb6e70b38cf3a6a2a76b3aff59a379040568108ef2624c502bdf7a28f2cff7f91483a3f6586ee8eb1c76ccd0b821646cbd1d65b09cda90dcad627824293ee00c2afd81276f1e625
chimera bugs
chimera-bugs@cgl.ucsf.edu
2026-06-24
13:03 PDT
----------------------------------------------------------------------------------------------
Quarantined (by Score)
----------------------------------------------------------------------------------------------
Address: Voice Call <quickbooks@notification.intuit.com>, quickbooks@notification.intuit.com
Subject: ☎️ You have received a voicemail from +1***-405-4098)- 6/24/2026 7:51:06 p.m.
Delivery Date/Time: 24 Jun 26 - 10:51
Contact Administrator to take action on this email
https://us5.proofpointessentials.com/app/digest.php?ts=1782331391&action=hp&a_id=4ibed484b6f0c72c25a423e1f45537cce236ec3fac05ca8caa5ca1907ca25a0e7ee00bf18d19d4153b4eb8b65b139e46ed18565e0b6d2b46e2ac9e86f317bc0a96ae
Sign in to your account: https://us5.proofpointessentials.com/app/login.php?ts=1782331391&e_uuid=4ibe1d017b4cb6e70b38cf3a6a2a76b3aff59a379040568108ef2624c502bdf7a28f2cff7f91483a3f6586ee8eb1c76ccd0b821646cbd1d65b09cda90dcad627824293ee00c2afd81276f1e625
Request New Digest: https://us5.proofpointessentials.com/app/digest.php?action=request&k=k1&payload=4i46e13238f6f9479b8204685fcd2170cdf802b06945f63ab0001534f01f261ab840a31022cec448ab5f67d270d71788a9df5e287ec4f3a58359351d53ec8698e847856aa47aa7dd5a80d9caefe36114432bc4f523b6975a696011a0ec748a7e2b9cd33a0282a0bda05755bf5925100c78980d593492dcc462aa2c2f9c2cd53285a9c2f20a8bb31fcc5a6c29538e7ba9ae7176e7b13a04eb57345de5fee482c84bf14922752bd33cefae7eaebb7dedeb01f23603ff3054d87e0c4702758589e37457b77567cc76d676ba9b2dc6637576bd17b0989504c92acfae19c3904a3d3c91efdac0928d263d0af83683250219c0f841519f7c3bb1905f604e68a010096f1ad67740dc69dd7bc42a139a05db168437477c21&e_uuid=4ibe1d017b4cb6e70b38cf3a6a2a76b3aff59a379040568108ef2624c502bdf7a28f2cff7f91483a3f6586ee8eb1c76ccd0b821646cbd1d65b09cda90dcad627824293ee00c2afd81276f1e625&a_id=4ibed484b6f0c72c25a423e1f45537cce236ec3fac05ca8caa5ca1907ca25a0e7ee00bf18d19d4153b4eb8b65b139e46ed18565e0b6d2b46e2ac9e86f317bc0a96ae
https://www.proofpoint.com/us/products/essentials
© Proofpoint, Inc. 2004-2026All Rights Reserved
|
|||
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
