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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#381 fixed Cameron Byrne feedback on draft-iab-protocol-transitions-05 draft-iab-protocol-transitions@… Byrne, Cameron <Cameron.Byrne@…>
#380 fixed Brian Carpenter's comments on draft-iab-protocol-transitions-00 dthaler@… brian.e.carpenter@…
#379 fixed Russ White comments dthaler@… alcoop@…
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 367)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#381 fixed Cameron Byrne feedback on draft-iab-protocol-transitions-05 draft-iab-protocol-transitions@… Byrne, Cameron <Cameron.Byrne@…>
Description

I consider myself one of the early instigators of world ipv6 day, if not the earliest. I floated the idea at an isoc event / round table in Seattle. The problem was economic, not technical. And, your i-d should emphasize that. The altruistic dual-stack approach failed, and economic market forces slowed adoption as each actor waited for someone else to absorb the cost of launching ipv6.

In 2011, there was the common belief that launching ipv6 would break ~1% of users

I heard yahoo and google say their primary impediment of launching was they could not break 1% of users and lose 1% of revenue because customers have zero loyalty and zero economic switching cost. If google fails, use bing. If yahoo fails use google, and so on. Nobody wanted to give 1% to their competitor in the name of IPv6.

So the reward for launching ipv6 early was a gift to your competitors. This was a business deal breaker.

The genius of world ipv6 launch is that an anti-competitive monopoly / union was formed. But yahoo, google, and bing all enabling ipv6 at the same time, the cost of failure was not transferred between competitors, the cost of failing ipv6 was passed to the consumer. Consumers with broke ipv6 connectivity could not pursue a zero cost switch to a competitor. Bing, yahoo, and google were all broken at the same time to a user with impaired ipv6. The user has to accept the issue was on their end , and the consumer had to assume the cost of fixing (disabled ipv6 on the pc ...).

Economic incentives to reduce latency also pushed SPDY / QUIC / HTTP2. It is well known folk-lore in tech that decreasing latency drives up revenue, the business approves of these methods.

#380 fixed Brian Carpenter's comments on draft-iab-protocol-transitions-00 dthaler@… brian.e.carpenter@…
Description

Sent: Monday, October 19, 2015 11:03 AM

  1. Translation Plans

I think that section title is an entertaining slip of the keyboard.

  1. Security Considerations

I agree that translators can be targets for attack. But I think coexistence in general increases risk: viewed globally, it doubles the attack surface, and allows attacks that exploit the weaker of the two protocols by claiming not to understand the stronger one.

Also, I think there's quite a lot of resonance between transition issues and extension issues, so you might find some of the thinking in RFC 6709 to be relevant. For a start, a protocol with well designed extensibility could avoid the need for any transition; and a protocol with poor extensibility might be the direct cause of a transition.

I'm thinking that this document needs some case studies; most of the meat in RFC 6709 came from the case studies.

#379 fixed Russ White comments dthaler@… alcoop@…
Description

On 5/19/14, 9:49 AM, "Russ White" <russ@…> wrote:

Y'all:

Just one comment (probably minor)... In section two, you've used "firewalls" as a filtering example. I don't know that I know what a "firewall" is any longer... :-) The services that used to be bundled into a firewall have been broken apart in so many places and so many ways that it might be better to describe the services normally found on a firewall as individual types of filtering (directional port filtering, NAT, deep packet inspection, etc.). I think it would probably make this section a little more clear, or rather provide more specific examples of what you're trying to say here. It also adds confusion in that "firewalls" often perform "web filtering," and "spam filtering" in the following paragraphs.

Maybe something like this:

Forwarding Plane Filtering: Packet and flow level filtering are employed to block or control service access at many points in today's internet [RFC2979]. Typically, forwarding plane filters block according to content-neutral rules; e.g., blocking all connections on specific ports, protocols, or network layer addresses. More advanced configurations perform deep packet inspection, block inbound traffic for flows that have not been established, block packets or flows based on the content carried, or include other forms of packet or flow based rule sets. Many packet filters implement web based filtering capabilities (see below). Forwarding plane filtering is deployed on forwarding devices throughout the network (but particularly at the network edge), specialized appliances or services, and on individual hosts connected to the network.

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 6 years ago Last modified on 06/11/16 16:52:55