Trac Ticket Queries

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.

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:

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

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

1 2 3 →

Ticket	Resolution	Summary	Owner	Reporter
#33	fixed	Segfault in atmosphere processing	somebody	dbaack
#22	wontfix	fscctrl responsible for bias patch temperatures?	somebody	dneise
#21	wontfix	FACT version of Corsika/MMCS in SVN	somebody	dneise

1 2 3 →

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

1 2 3 →

Ticket	Resolution	Summary	Owner	Reporter
#33	fixed	Segfault in atmosphere processing	somebody	dbaack
Description	I get following segmentation fault for some EventIO files and I cant find the reason: ROOT:Error: segmentation violation =========================================================== There was a crash. This is the entire stack trace of all threads: =========================================================== #0 0x00007fe2859e9b0c in waitpid () from /lib64/libc.so.6 #1 0x00007fe28596e092 in do_system () from /lib64/libc.so.6 #2 0x00007fe28af4a8d9 in TUnixSystem::StackTrace (this=0x1797bc0) at /home/dbaack/root/root_v5.34.36/core/unix/src/TUnixSystem.cxx:2419 #3 0x00007fe28af4c51c in TUnixSystem::DispatchSignals (this=0x1797bc0, sig=kSigSegmentationViolation) at /home/dbaack/root/root_v5.34.36/core/unix/src/TUnixSystem.cxx:1294 #4 <signal handler called> #5 0x00007fe28c5bf984 in MSimAtmosphere::Process() () from libmars.so #6 0x00007fe28c195df4 in MTask::CallProcess() () from libmars.so #7 0x00007fe28c194707 in MTaskList::ProcessTaskList() () from libmars.so #8 0x00007fe28c194ba8 in MTaskList::Process() () from libmars.so #9 0x00007fe28c195df4 in MTask::CallProcess() () from libmars.so #10 0x00007fe28c151e45 in MEvtLoop::Process(unsigned int) () from libmars.so #11 0x00007fe28c152344 in MEvtLoop::Eventloop(unsigned int, MEvtLoop::Statistics_t) () from libmars.so #12 0x00007fe28c852d20 in MJSimulation::Process(MArgs const&, MSequence const&) () from libmars.so #13 0x00000000004043bb in main () =========================================================== Simulation Settings: (Atmosphere should be handled by ceres) RUNNR 104 EVTNR 1 NSHOW 4000 SEED 1041 0 0 SEED 1042 0 0 SEED 1043 0 0 SEED 1044 0 0 SEED 1045 0 0 THETAP 10 10 PRMPAR 14 ERANGE 100 30000 ESLOPE -2.0 PHIP 0 0 VIEWCONE 0 5 FIXCHI 0 OBSLEV 220000 MAGNET 30.3 24.1 ARRANG -7 ATMOSPHERE 7 T ATMLAY 775000 1650000 5000000 10500000 RADNKG 20000 ECUTS 0.3 0.3 0.02 0.02 ECTMAP 10000 MUADDI 0 MUMULT 1 CWAVLG 290 900 CERSIZ 1 CERFIL 1 CSCAT 1 60000.0 0.0 DYNSTACK 1000000 TELESCOPE 0 0 0 500 LONGI 0 20 0 0 MAXPRT 0 PAROUT 0 0 DATBAS 0 DEBUG F 6 F 1000000 DIRECT ./ FLUDBG F TELFIL cerdata USER dominik EXIT I can upload the corsika file somewhere if needed
#22	wontfix	fscctrl responsible for bias patch temperatures?	somebody	dneise
Description	The FACT++ program fscctrl, which connects to the FSC board, receives and interprets the FSC-messages, checks the checksums and finally publishes the recieved information. But I just found, that it also interpolates the temperatures of the 320 bias patches (a bias path is "one half" of a trigger patch, a group of either 4 or 5 pixels) from the measured temperatures. I think this code should be moved outside of fscctrl, since not every FSC in the world might have the same number of sensors attached, nor might it even be possible to interpolate anything useful. Of course I see, that from a viewpoint of dependency, one might have the impression this calculation may be put into the program fscctrl, since this program happens to know all the necessary information to do the calculation. fscctrl needs a file called "bias-positions.txt". Naively one does not understand, why the program, that is expected to listen to the FSC board, needs to know anything about the existence or position or number of bias patches. Also the program biasctrl, which happens to know how many motherboards are connected to the the bias-crate, might not really know how many channels are used in the camera. So in a word, I think one should extract this code, into another program, that is acting on a more abstract level.
#21	wontfix	FACT version of Corsika/MMCS in SVN	somebody	dneise
Description	Recently I got asked, where in the FACT SVN one can find the version of Corsika/MMCS we are using. I had no answer to that question, so I checked it in in r18024 into this place: https://trac.fact-project.org/browser/trunk/mmcs6500 In order to successfully install/use this version, please refer to the README file. In order to quickly get Corsika running, one needs some binary tables, which are generated by Corsika at its very first run, in case they are missing, it takes an entire day or even longer (I didn't measure the time). So the file should be provided as well. As a courtesy to the end user say. But since it can be generated, it should imho not be versioned, so I've put it here ​http://fact-project.org/mmcs6500_bin/ for easy download. The file should be downloaded into the mmcs6500 folder, be unzipped, and one is ready to go... I will put this information into a README file as well. For propoer installation of this corsika version, fluka is needed to be downloaded from ​http://www.fluka.org/fluka.php and installed prior to building mmcs6500. I think this is not mentioned properly in the README as well. So I propose to rewrite the README for FACTies, after that, I think this ticket can be closed ... I might do it in a few hours, but I wanted to get this checked in and done as quickly as possible.

1 2 3 →

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