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

Some shortcuts can be used to manipulate checkbox filters.

  • Clicking on a filter row label toggles all checkboxes.
  • Pressing the modifier key while clicking on a filter row label inverts the state of all checkboxes.
  • Pressing the modifier key while clicking on a checkbox selects the checkbox and deselects all other checkboxes in the filter.

The modifier key is platform and browser dependent. On Mac the modified key is Option/Alt or Command. On Linux the modifier key is Ctrl + Alt. Opera on Windows seems to use Ctrl + Alt, while Alt is effective for other Windows browsers.

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1263 wontfix Notice of Claimed Infringement from 31.133.141.218 at 2018-11-14T04:01:40Z - Ref. b791819e1fa17fd4ae21 < default > notice@…
#1257 wontfix Your server 31.133.188.165 has been registered as an attack source llynch@… anonymous
#1256 wontfix Message Received: (IPE-Ticket #780614) Notice of Claimed Infringement - Case ID c66f1d22cb2b4c222931 < default > anonymous
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 849)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1263 wontfix Notice of Claimed Infringement from 31.133.141.218 at 2018-11-14T04:01:40Z - Ref. b791819e1fa17fd4ae21 < default > notice@…
Description
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear Internet Society,

This message is sent on behalf of HOME BOX OFFICE, INC. ("HBO").

We have information leading us to believe that the IP address 31.133.141.218 was used to download or share Game of Thrones without authorization (additional details are listed below).  HBO owns the copyright or exclusive rights to Game of Thrones, and the unauthorized download or distribution constitutes copyright infringement.  Downloading unauthorized or unknown content is also a security risk for computers, devices, and networks.

As the owner of the IP address, HBO requests that Internet Society immediately contact the subscriber who was assigned the IP address at the date and time below with the details of this notice, and take the proper steps to prevent further downloading or sharing of unauthorized content and additional infringement notices.

We also encourage you to inform the subscriber that HBO programming can easily be watched and streamed on many devices legally by adding HBO to the subscriber’s television package.

We have a good faith belief that use of the copyrighted material detailed below is not authorized by the copyright owner, its agent, or the law.  The information in this notice is accurate and we state, under penalty of perjury, that we are authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.  This letter is not a complete statement of HBO's rights in connection with this matter, and nothing contained herein constitutes an express or implied wavier of any rights or remedies of HBO in connection with this matter, all of which are expressly reserved.

We appreciate your assistance and thank you for your cooperation in this matter.  Your prompt response is requested.  Any further enquiries can be directed to notice@hbo.copyright-notice.com.  Please include this message with your enquiry to ensure a quick response.

Respectfully,

Brad Bo
On behalf of Home Box Office, Inc.
2880 Lakeside Drive, Suite 360
Santa Clara, CA 95054
E-mail: notice@hbo.copyright-notice.com

- ------------- Infringement Details ----------------------------------
Title:        Game of Thrones
Timestamp:    2018-11-14T04:01:40Z
IP Address:   31.133.141.218
Port:         10013
Type:         BitTorrent
Torrent Hash: 1858991eb4269a3459363d891eaa7625271afe3f
Filename:     Game.of.Thrones.S05
Filesize:     42329 MB
- ---------------------------------------------------------------------


<?xml version="1.0" encoding="UTF-8"?>
<Infringement xmlns="http://www.acns.net/ACNS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.acns.net/ACNS http://www.acns.net/v1.2/ACNS2v1_2.xsd">
  <Case>
    <ID>b791819e1fa17fd4ae21</ID>
    <Status>Open</Status>
    <Severity>Normal</Severity>
  </Case>
  <Complainant>
    <Entity>Home Box Office, Inc.</Entity>
    <Contact>Vobile - Compliance</Contact>
    <Address>2880 Lakeside Drive, Suite 360
Santa Clara, CA 95054</Address>
    <Phone>+1 (408) 492 1100</Phone>
    <Email>notice@hbo.copyright-notice.com</Email>
  </Complainant>
  <Service_Provider>
    <Entity>Internet Society</Entity>
    <Email>tickets@meeting.ietf.org</Email>
  </Service_Provider>
  <Source>
    <TimeStamp>2018-11-14T04:01:40Z</TimeStamp>
    <IP_Address>31.133.141.218</IP_Address>
    <Port>10013</Port>
    <Type>BitTorrent</Type>
    <SubType BaseType="P2P" Protocol="BITTORRENT"/>
    <Number_Files>1</Number_Files>
  </Source>
  <Content>
    <Item>
      <TimeStamp>2018-11-14T04:01:40Z</TimeStamp>
      <Title>Game of Thrones</Title>
      <FileName>Game.of.Thrones.S05</FileName>
      <FileSize>44385271571</FileSize>
      <Hash Type="SHA1">1858991eb4269a3459363d891eaa7625271afe3f</Hash>
    </Item>
  </Content>
</Infringement>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJb6540AAoJEN5LM3Etqs/WkKgIAK2T16wM8NCfbLxmc1N5J1Yg
XBmcsu99GwPcfT7nN51lNB8floQLPoOp5fEdVXFLHbWQftqyxBDiVoQ2PFv/siWV
1frnUWxOlMiWxHySCAHLGxTE9bWA2zGQYSbdanxaB0rTsx1i+48OaGiYlPva9BGA
OCLKgaW/7aXjHslOUbFerCQRuEJOaW4UM3vEc7+NzTFduJYOc8GKcXf9fgJj5BIv
wNleNZqcBNl00wnCP/wnRaEGf5aa/TCOTH67hP3AVuAN3Soys45qPo8hF1LW0MXW
BL1mjklljarP62Ooz+b7ADft9q+IeuAUd1O9sbyT9WI+bIGU34jbZTWRlSnZ1l0=
=xRqM
-----END PGP SIGNATURE-----

b791819e1fa17fd4ae21.xml

#1257 wontfix Your server 31.133.188.165 has been registered as an attack source llynch@… anonymous
Description
Dear Provider,


I’m George Egri, the Co-Founder and CEO of BitNinja Server Security. I’m writing to inform you that we have detected malicious requests from the IP 31.133.188.165 directed at our clients’ servers.


As a result of these attacks, we have added your IP to our greylist to prevent it from attacking our clients’ servers.


Servers are increasingly exposed as the targets of botnet attacks and you might not be aware that your server is being used as a “bot” to send malicious attacks over the Internet.


I've collected the 3 earliest logs below, and you can find the freshest 100, that may help you disinfect your server, under the link.
http://bitninja.io/incidentReport.php?details=0b16a1a44c2b1f02f2?utm_source=incident&utm_content=publicpage. The timezone is UTC +1:00.

<pre style='padding:10px 20px; background:#e6e6e6;margin-bottom:10px'>{
    "PORT HIT": "31.133.188.165:49298-&gt;69.175.109.50:23"
}</pre><pre style='padding:10px 20px; background:#e6e6e6;margin-bottom:10px'>{
    "PORT HIT": "31.133.188.165:54046-&gt;199.168.186.10:23"
}</pre><pre style='padding:10px 20px; background:#e6e6e6;margin-bottom:10px'>{
    "PORT HIT": "31.133.188.165:54077-&gt;199.168.186.10:23"
}</pre>

Please keep in mind that after the first intrusion we log all traffic between your server and the BitNinja-protected servers until the IP is removed from the greylist. This means you may see valid logs beside the malicious actions in the link above. If you need help finding the malicious logs, please don’t hesitate to contact our incident experts by replying to this e-mail.

For more information on analyzing and understanding outbound traffic, check out this:
https://doc.bitninja.io/_images/bitninja-incident-report-1.jpg?utm_source=incident&utm_campaign=investigation&utm_content=image

We’ve also dedicated an entire site help people prevent their server from sending malicious attacks: 
https://doc.bitninja.io/investigations.html?utm_source=incident&utm_campaign=investigation&utm_content=documentation


Thank you for helping us make the Internet a safer place!


Regards,


George Egri
CEO at BitNinja.io

BitNinja.io @ BusinessInsider UK

BitNinja.io hits the WHIR.com
BitNinja @ CodeMash conference

Added by email2trac

Added by email2trac

#1256 wontfix Message Received: (IPE-Ticket #780614) Notice of Claimed Infringement - Case ID c66f1d22cb2b4c222931 < default > anonymous
Description
 --------------------

Dear IETF,

Your message (Notice of Claimed Infringement - Case ID
c66f1d22cb2b4c222931) has been received and we'll try and get back to you
in the next 24 hours.

If your enquiry is about a copyright infringement notice, please send a
copy of the notice you received from your Internet Service Provider. We
need the "Case ID" from the notice in order to provide you additional
information. You can reply to this email and include a copy of the notice
to update the ticket.

Sincerely,
IP-Echelon Support
[V0VG92-YQGZ]
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 2 years ago Last modified on 25 Jan 2017, 21:56:44