wiki:TracQuery

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

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

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#117 fixed Add optional SPF <human_result> to aggregate report schema alex_brotman@… mail@…
#114 wontfix RFC 8020 implementation is lacking dougfoster.emailstandards@…
#110 invalid Implicit MX hinders Non-Existent domain checks dougfoster.emailstandards@…
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>:

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#117 fixed Add optional SPF <human_result> to aggregate report schema alex_brotman@… mail@…
Description

Add optional <human_result> field to <auth_results><spf> section, analogous to the existing field in <auth_results><dkim>.

Example:

<auth_results>
	<spf>
		<domain>example.net</domain>
		<scope>mfrom</scope>
		<result>permerror</result>
		<human_result>Syntax error in SPF record</human_result>
	</spf>
</auth_results>

Justification: A free text string <human_result> allows to add a meaningful error message in case when the SPF result is permerror or temperror. This can be used as signaling mechanism, especially when the error is not obvious or does not occur with every mail receiver (subject to how strict they interpret the SPF spec and how they handle minor errors).

Here are a couple of real-world examples (anonymized) during SPF checks that have been all subsumed as permerror:

  • "example.net: Maximum DNS-interactive terms limit (10) exceeded"
  • "example.net ... example.com: Maximum DNS-interactive terms limit (10) exceeded"
  • "example.net: Redundant applicable 'v=spf1' sender policies found"
  • "example.net: Included domain 'example.com' has no applicable sender policy"
  • "mail.example.net: Junk encountered in record 'v=spf1 a mx ip4:192.0.2.1 ip4:192.0.2.51 ~all|'"
  • "example.net: Junk encountered in record 'v=spf1 ip4:192.0.2.1 ip4:192.0.2.51 include:_spf.example.com <http://spf.example.com> ~all'"
  • "example.net: Missing required domain-spec in 'Include:'"

Note that there are different interpretations of how to count the number of DNS lookups: <https://www.mail-archive.com/dmarc-discuss@dmarc.org/msg03268.html>

Examples for temperror:

  • "example.net: 'SERVFAIL' error on DNS 'TXT' lookup of 'example.net'"
  • "email.example.net: 'SERVFAIL' error on DNS 'TXT' lookup of 'email.example.net'"
  • "example.net: 'SERVFAIL' error on DNS 'PTR' lookup of '1.2.0.192.in-addr.arpa'"

The name <human_result> has been chosen, because it already exists for the <dkim> section.

#114 wontfix RFC 8020 implementation is lacking dougfoster.emailstandards@…
Description

Regarding this section:

3.8. Non-existent Domains

For DMARC purposes, a non-existent domain is a domain for which there is an NXDOMAIN or NODATA response for A, AAAA, and MX records. This is a broader definition than that in [RFC8020].

It seems worth noting that RFC 8020 is not reliably implemented, so that following RFC 8020 is not really an option.

In fact, I have not been able to find a DNS server which does comply with RFC 8020. My working example is email3.reachmd.com, and its child entry sg.email3.reachmd.com (a CNAME record) I have tested 8.8.8.8, 1.1.1.1, and an authoritative server for reachmd.com, and all return NXDomain. The child record is a CNAME which (depending on the moment) either returns an IP address or "No Data".

#110 invalid Implicit MX hinders Non-Existent domain checks dougfoster.emailstandards@…
Description

I assume that this will become a topic for Email Core, but should be discussed here first.

RFC 5321 specifies that if an MX does not exist, the sender should attempt sending to any A/AAAA record that matches the mail domain. An MX can only exist if the mail domain is a DNS domain, so a reasonable inference is that the authors were assuming that the A/AAAA record would also be a DNS domain, using a null host segment, so that the host name corresponded to the email domain. If that was the intent, it was not documented or enforced. As a result, any single host might be an email domain, and therefore the only valid test for the non-existence of an email domain is to demonstrate the absence of multiple records, including A/AAAA.

Single-host mail domains cannot implement SPF policies or DKIM signatures, but might be able to benefit from DMARC policies at the organizational level, and DKIM signatures from other domains in the organization.

I tested four different email products, and confirmed that all of them will attempt delivery to an A record which represents a single host within a parent domain, in compliance with the nominal language of RFC 5321.

When validating the RFC5322 From address with DMARC, the MX/A/AAAA test is a poor fit, because an email domain used exclusively for third-party mass mailings may have no use for either MX or A/AAAA. I am prepared to argue that the appropriate test is to evaluate the existence of the domain, by checking for an NXDomain result on a record type other than A/AAAA/CNAME. But the argument is moot if a single-host can be a legitimate email domain.

Questions:

Did IETF specifically intend to allow a single host to be an email domain, or can we begin requiring that an email domain always correspond to a DNS domain?

Does IETF intend to allow Implicit MX forever, or can we declare this a transition mechanism which is no longer needed?

Does anyone have information about the volume of email domains which depend on Implicit MX host records, and whether they are domains or single hosts?

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

Last modified 5 years ago Last modified on 05/11/16 15:46:33