TicketQuery Wiki Macro
The TicketQuery macro lets you display ticket information anywhere that accepts WikiFormatting.
The query language used by the [[TicketQuery]] macro is described in the TracQuery page.
Usage
[[TicketQuery]]
Wiki macro listing tickets that match certain criteria.
This macro accepts a comma-separated list of keyed parameters, in the form "key=value".
If the key is the name of a field, the value must use the syntax
of a filter specifier as defined in TracQuery#QueryLanguage.
Note that this is not the same as the simplified URL syntax
used for query: links starting with a ? character. Commas (,)
can be included in field values by escaping them with a backslash (\).
Groups of field constraints to be OR-ed together can be separated by a
literal or argument.
In addition to filters, several other named parameters can be used to control how the results are presented. All of them are optional.
The format parameter determines how the list of tickets is
presented:
- list -- the default presentation is to list the ticket ID next to the summary, with each ticket on a separate line.
- compact -- the tickets are presented as a comma-separated list of ticket IDs.
- count -- only the count of matching tickets is displayed
- rawcount -- only the count of matching tickets is displayed, not even with a link to the corresponding query (since 1.1.1)
- table -- a view similar to the custom query view (but without the controls)
- progress -- a view similar to the milestone progress bars
The max parameter can be used to limit the number of tickets shown
(defaults to 0, i.e. no maximum).
The order parameter sets the field used for ordering tickets
(defaults to id).
The desc parameter indicates whether the order of the tickets
should be reversed (defaults to false).
The group parameter sets the field used for grouping tickets
(defaults to not being set).
The groupdesc parameter indicates whether the natural display
order of the groups should be reversed (defaults to false).
The verbose parameter can be set to a true value in order to
get the description for the listed tickets. For table format only.
deprecated in favor of the rows parameter
The rows parameter can be used to specify which field(s) should
be viewed as a row, e.g. rows=description|summary
The col parameter can be used to specify which fields should
be viewed as columns. For table format only.
For compatibility with Trac 0.10, if there's a last positional parameter
given to the macro, it will be used to specify the format.
Also, using "&" as a field separator still works (except for order)
but is deprecated.
Examples
| Example | Result | Macro |
|---|---|---|
| Number of Triage tickets: | 20 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 33 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 0 | [[TicketQuery(status=reopened,count)]]
|
| Number of assigned tickets: | 0 | [[TicketQuery(status=assigned,count)]]
|
| Number of invalid tickets: | 1 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 0 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 0 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 2 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 4 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 21 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 41 | [[TicketQuery(count)]]
|
| Number of tickets reported or owned by current user: | 0 | [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
|
| Number of tickets created this month: | 0 | [[TicketQuery(created=thismonth..,count)]]
|
| Number of closed Firefox tickets: | 0 | [[TicketQuery(status=closed,keywords~=firefox,count)]]
|
| Number of closed Opera tickets: | 0 | [[TicketQuery(status=closed,keywords~=opera,count)]]
|
| Number of closed tickets affecting Firefox and Opera: | 0 | [[TicketQuery(status=closed,keywords~=firefox opera,count)]]
|
| Number of closed tickets affecting Firefox or Opera: | 0 | [[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
|
| Number of tickets that affect Firefox or are closed and affect Opera: | 0 | [[TicketQuery(status=closed,keywords~=opera,or,keywords~=firefox,count)]]
|
| Number of closed Firefox tickets that don't affect Opera: | 0 | [[TicketQuery(status=closed,keywords~=firefox -opera,count)]]
|
| Last 3 modified tickets: | #41, #40, #38 | [[TicketQuery(max=3,order=modified,desc=1,compact)]]
|
Details of ticket #1: |
| |
| ||
Format: list
[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
This is displayed as:
No results
[[TicketQuery(id=123)]]
This is displayed as:
No results
Format: compact
[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
This is displayed as:
No results
Format: count
[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
This is displayed as:
Format: progress
[[TicketQuery(milestone=0.12.8&group=type,format=progress)]]
This is displayed as:
Format: table
You can choose the columns displayed in the table format (format=table) using col=<field>. You can specify multiple fields and the order they are displayed 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)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #33 | fixed | Segfault in atmosphere processing | ||
| #22 | wontfix | fscctrl responsible for bias patch temperatures? | ||
| #21 | wontfix | FACT version of Corsika/MMCS in SVN |
Full rows
In table format you can specify full rows 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)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #33 | fixed | Segfault in atmosphere processing | ||
| 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? | ||
| 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 | ||
| 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. |
|||
See also: TracQuery, TracTickets, TracReports
