wiki:TracQuery

Trac Ticket Queries

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.

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.

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:

#98
Problems after 12hrs during LAM run
#129
UM ERROR in U_MODEL (error code 4)
#139
devt quota
#198
Start dumps for HECToR run
#236
Error message
#380
Problem with global job for LAM
#384
Processing UM output files to netcdf format
#516
Ensmble run using HiGEM1.2 is doing the job for run member at a time and getting terminated
#615
GHUI errors and warning
#926
Compilation error for UM7.3
#1470
"UNRECOVERABLE library error" in makeBC run.
#1563
N512 job ported to Monsoon?
#1672
error when running umui
#1717
UM-UKCA v8.4 ARCHER job xlrfv reconfiguration cannot find STASH section 34-163 in dump (but it's there!)
#1987
Setting up ensemble simulations
#2024
UKCA job runs for 16 days and then walltime is exceeded
#2093
Cannot submit on ARCHER
#2154
Problem with a Global Reconfiguration job
#2228
Fail to submit a standard job from PUMA
#2254
UM parallel running problem
#2419
Disk quota increase
#2492
Error in buffin errorCode= 3.
#2500
Unrecognised in namelist input
#2542
vegetation Leaf Area Index (LAI) for each Plant Functional Type (PFT): December anomaly
#2592
postproc timeout
#2639
Soil Moisture benchmark data and model variable for ILAMB
#2738
Reconfiguration failure
#2779
Model still failing after this morning's reboot.
#2926
iPython
#2992
um-atmos recon threading levels and defensive checks
#3098
Shortcut to saved session
#3105
RosePOpenError - Nested Suite Tutorial 2019
#3122
Restarting suite
#3198
cannot log onto ARCHER account
#3321
UM Version 11.5 not available in CMS Helpdesk options

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. This also allows displaying the link and description of a single ticket:

[[TicketQuery(id=123)]]

This is displayed as:

#123
DEVT space

A more compact representation without the ticket summaries is also available:

[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]

This is displayed as:

#98, #129, #139, #198, #236, #380, #384, #516, #615, #926, #1470, #1563, #1672, #1717, #1987, #2024, #2093, #2154, #2228, #2254, #2419, #2492, #2500, #2542, #2592, #2639, #2738, #2779, #2926, #2992, #3098, #3105, #3122, #3198, #3321

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:

35

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#3333 fixed reconfiguration and the North/South halos too small for advection error um_support ggxmy
#3329 answered SoilGrids data, SOL_ZMX pmcguire pmcguire
#3328 fixed PUMA no longer connecting to ARCHER um_support alwalsh
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 3267)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#3333 fixed reconfiguration and the North/South halos too small for advection error um_support ggxmy
Description

Dear Helpdesk,

In #3319 I said I had a trouble with the "North/South? halos too small for advection" error in the first few minutes (8 minutes precisely speaking) of the process 'coupled'. That was resolved after I downloaded the dump file again. I said the dump file was corrupted again because I had had a trouble before with the same suite or the similar one (#3203) and it was resolved after I newly copied the dump file.

Now I'm trying to run the suite with dump/restart files at different years. I tried 20140101 ones (five files) instead of 20150101 ones with reconfiguration turned on (u-bw426). I had the halos error.

So I made a new suite (u-bw458) to test things by copying my running suite (u-bv563). I just turned on reconfiguration and left everything else as it is. It uses 2015 files. When I try to run it it got the halos error. Then I turned off reconfiguration and the run failed with the halos error! (u-bw458) I went back to u-bv563 that ran OK yesterday and tried running it (with reconfiguration turned off) and it failed with the halos error!

It looks like reconfiguration updates the dump file.

-rw-r--r--. 1 myosh asci       7012302848 Jul 28 09:14 bg466a.da20150101_00

Doesn't this suggest reconfiguration somehow modifies the dump file so that it causes the halos error?

Please can you help me? My plan is to make an ensemble of size 10 or so starting from 2015, using dump files from the historical ensemble of size 4. So I'm going to use 4 dump files from each of 2015, 2014 and 2013. Is there a way to prevent reconfiguration from damaging(?) the dump file? Or is there a way to use a dump file of a wrong date without doing reconfiguration?

Best regards, Masaru

#3329 answered SoilGrids data, SOL_ZMX pmcguire pmcguire
Description

Hi Patrick,

I had a meeting with AnneV yesterday (June 10) and we went through the SoilGrids data. We found that the rooting depth SOL_ZMX are not available in the SoilGrids database but these are available in the datasets you prepared. She asked to contact you to know where you got these data from.

Thanks.

Maleki

#3328 fixed PUMA no longer connecting to ARCHER um_support alwalsh
Description

Hi,

Since PUMA has been put back online after yesterdays maintenance, I can no longer ssh to ARCHER. The ssh command hangs indefinitely and cylc also does not seem to be communicating with ARCHER (cylc job state doesn't reflect actual state of jobs).

I am able to connect to ARCHER locally so believe the issue is with PUMA. Many thanks for any help in resolving this.

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

Last modified 8 years ago Last modified on 09/01/13 14:15:57