wiki:

TracQuery


Version 1 (modified by trac, 5 years ago) (diff)

--

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.

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:

No results

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.

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

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

This is displayed as:

No results

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:

0

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#5739 needs_more_info Invalid RTCP SR package sent by ffmpeg sancane
#5730 invalid Rewrapping H.264 MXF file from camera Sony FS 7 creates file not playable by Quicktime rmk
#5729 fixed FLV key frame index at start may be skipped snorlaxzxz
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 4338)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#5739 needs_more_info Invalid RTCP SR package sent by ffmpeg sancane
Description

Summary of the bug: ffmpeg is sending an invalid RTCP SR packet, we detected that with the version 2.8.6 of ffmpeg, the RTCP SR sent by ffmpeg does not increment the ntptime, as we could expect so the clock is supposed to be monotonic, This makes it impossible to use RTCP SRs to synchronize. It seems to be a regression from any commit introduced from version 2.7.2 wich were doing it well.

Next is the information about SR sent with ffmpeg 2.8.6:

0:00:41.314525104 Received RTCP SR packet SSRC: 535359325, rtptime: 3030375347, ntptime: 9223372036854775808, ntpnstime: 596523:14:08.000000000
0:00:46.323753635 Received RTCP SR packet SSRC: 535359325, rtptime: 3030826067, ntptime: 9223372036854775808, ntpnstime: 596523:14:08.000000000
0:00:51.355472637 Received RTCP SR packet SSRC: 535359325, rtptime: 3031278947, ntptime: 9223372036854775808, ntpnstime: 596523:14:08.000000000
0:00:56.391561089 Received RTCP SR packet SSRC: 535359325, rtptime: 3031732097, ntptime: 9223372036854775808, ntpnstime: 596523:14:08.000000000
0:01:01.422186827 Received RTCP SR packet SSRC: 535359325, rtptime: 3032184797, ntptime: 9223372036854775808, ntpnstime: 596523:14:08.000000000

Here is the one captured with ffmpeg 2.7.2:

0:00:50.725134082 Received RTCP SR packet SSRC: 2102232704, rtptime: 2173288374, ntptime: 15799514243063691084, ntpnstime: 1021836:24:30.631000000
0:00:55.757820842 Received RTCP SR packet SSRC: 2102232704, rtptime: 2173741254, ntptime: 15799514264675966517, ntpnstime: 1021836:24:35.662999999
0:01:00.760914175 Received RTCP SR packet SSRC: 2102232704, rtptime: 2174191524, ntptime: 15799514286163687899, ntpnstime: 1021836:24:40.665999999
0:01:05.793591156 Received RTCP SR packet SSRC: 2102232704, rtptime: 2174644494, ntptime: 15799514307780258300, ntpnstime: 1021836:24:45.699000000
0:01:10.819718742 Received RTCP SR packet SSRC: 2102232704, rtptime: 2175096834, ntptime: 15799514329366763930, ntpnstime: 1021836:24:50.725000000

How to reproduce:

% ffmpeg -re -i -an -vcodec libx264 -profile:v baseline -level 3.0 -f rtp rtp://SERVER_IP:PORT
ffmpeg version 2.8.6
built on ubuntu xenial
#5730 invalid Rewrapping H.264 MXF file from camera Sony FS 7 creates file not playable by Quicktime rmk
Description

How to reproduce:

ffmpeg -i ~/lesspain/samples/cameras/sony/pxw_fs7/sony_pxw_fs7_1080_xavc_2997p_13s.MXF -y -an -c:v copy sony_pxw_fs7_1080_xavc_2997p_13s-ffmpeg-rewrap-video-only.mov
ffmpeg version N-81077-g640c096 Copyright (c) 2000-2016 the FFmpeg developers
  built with Apple LLVM version 7.0.2 (clang-700.1.81)
  configuration: 
  libavutil      55. 28.100 / 55. 28.100
  libavcodec     57. 50.100 / 57. 50.100
  libavformat    57. 44.100 / 57. 44.100
  libavdevice    57.  0.102 / 57.  0.102
  libavfilter     6. 47.100 /  6. 47.100
  libswscale      4.  1.100 /  4.  1.100
  libswresample   2.  1.100 /  2.  1.100
[h264 @ 0x7fb0b2001600] Truncating likely oversized PPS
    Last message repeated 9 times
Guessed Channel Layout for Input Stream #0.1 : mono
Guessed Channel Layout for Input Stream #0.2 : mono
Guessed Channel Layout for Input Stream #0.3 : mono
Guessed Channel Layout for Input Stream #0.4 : mono
Guessed Channel Layout for Input Stream #0.5 : mono
Guessed Channel Layout for Input Stream #0.6 : mono
Guessed Channel Layout for Input Stream #0.7 : mono
Guessed Channel Layout for Input Stream #0.8 : mono
Input #0, mxf, from '/Users/krueger/lesspain/samples/cameras/sony/pxw_fs7/sony_pxw_fs7_1080_xavc_2997p_13s.MXF':
  Metadata:
    uid             : 791517d2-264c-11e6-826b-0800469995c2
    generation_uid  : 791517dc-264c-11e6-8829-0800469995c2
    company_name    : Sony
    product_name    : Mem 
    product_version : 2.00
    product_uid     : cede1104-8280-11de-8a39-08004678031c
    modification_date: 2016-05-30 09:54:17
    material_package_umid: 0x060A2B340101010501010D43130000000FA7A669387505D208004602029995C2
    timecode        : 00:00:57;20
  Duration: 00:00:13.68, start: 0.000000, bitrate: 123923 kb/s
    Stream #0:0: Video: h264 (High 4:2:2 Intra), yuv422p10le(pc, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 29.97 tbn, 59.94 tbc
    Metadata:
      file_package_umid: 0x060A2B340101010501010D431300000010A7A669387505D208004602029995C2
    Stream #0:1: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    Metadata:
      file_package_umid: 0x060A2B340101010501010D431300000010A7A669387505D208004602029995C2
    Stream #0:2: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    Metadata:
      file_package_umid: 0x060A2B340101010501010D431300000010A7A669387505D208004602029995C2
    Stream #0:3: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    Metadata:
      file_package_umid: 0x060A2B340101010501010D431300000010A7A669387505D208004602029995C2
    Stream #0:4: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    Metadata:
      file_package_umid: 0x060A2B340101010501010D431300000010A7A669387505D208004602029995C2
    Stream #0:5: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    Metadata:
      file_package_umid: 0x060A2B340101010501010D431300000010A7A669387505D208004602029995C2
    Stream #0:6: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    Metadata:
      file_package_umid: 0x060A2B340101010501010D431300000010A7A669387505D208004602029995C2
    Stream #0:7: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    Metadata:
      file_package_umid: 0x060A2B340101010501010D431300000010A7A669387505D208004602029995C2
    Stream #0:8: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s
    Metadata:
      file_package_umid: 0x060A2B340101010501010D431300000010A7A669387505D208004602029995C2
    Stream #0:9: Data: none
    Metadata:
      file_package_umid: 0x060A2B340101010501010D431300000010A7A669387505D208004602029995C2
      data_type       : vbi_vanc_smpte_436M
[mov @ 0x7fb0b1838600] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.
Output #0, mov, to 'sony_pxw_fs7_1080_xavc_2997p_13s-ffmpeg-rewrap-video-only.mov':
  Metadata:
    uid             : 791517d2-264c-11e6-826b-0800469995c2
    generation_uid  : 791517dc-264c-11e6-8829-0800469995c2
    company_name    : Sony
    product_name    : Mem 
    product_version : 2.00
    product_uid     : cede1104-8280-11de-8a39-08004678031c
    modification_date: 2016-05-30 09:54:17
    material_package_umid: 0x060A2B340101010501010D43130000000FA7A669387505D208004602029995C2
    timecode        : 00:00:57;20
    encoder         : Lavf57.44.100
    Stream #0:0: Video: h264 (avc1 / 0x31637661), yuv422p10le(pc, bt709), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 0.03 fps, 29.97 tbr, 30k tbn, 29.97 tbc
    Metadata:
      file_package_umid: 0x060A2B340101010501010D431300000010A7A669387505D208004602029995C2
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
Press [q] to stop, [?] for help
[NULL @ 0x7fb0b2001600] Truncating likely oversized PPS
    Last message repeated 399 times
[mov @ 0x7fb0b1838600] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
frame=  410 fps=0.0 q=-1.0 Lsize=  189217kB time=00:00:13.64 bitrate=113583.0kbits/s speed=27.3x    
video:189215kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.001157%

Then open the resulting file in Quicktime. It will refuse to open it and show an error dialog with the text "The file may be damaged or may not be a movie file compatible with Quicktime"

Sample can be downloaded at https://www.dropbox.com/s/l6jx4ymfeuga53z/sony_pxw_fs7_1080_xavc_2997p_13s.MXF?dl=1

Please note the warnings about "Truncating likely oversized PPS". The mov container of the resulting file looks ok at first glance compared to files that work but maybe the H.264 extradata is not parsed and then written correctly for some reason (just a wild guess).

#5729 fixed FLV key frame index at start may be skipped snorlaxzxz
Description

Summary of the bug: keyframe in metadata will be dropped until the first video frame comes.

How to reproduce:

seek attatched file.
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