wiki:

TracQuery


Version 1 (modified by trac, 7 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 5151)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#6912 invalid macOS - h264_videotoolbox encoder gives "No device available for encoder" warning alexpigment
#6906 fixed Re-order options for testsrc family of filters in manual Misaki
#6905 needs_more_info When copying video from .avi to .mp4, frames have incorrect pts values Misaki
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 5151)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#6912 invalid macOS - h264_videotoolbox encoder gives "No device available for encoder" warning alexpigment
Description

Summary of the bug:

When encoding with the h264_videotoolbox encoder on macOS, a warning is given that says "No device available for encoder (device type videotoolbox for codec h264_videotoolbox)". Since this message is confusing to users and potentially sounds like a software fallback is being used or something isn't configured correctly, it should be removed. Issue is similar to #6492.

How to reproduce:

% ffmpeg -f lavfi -i smptebars=size=1280x720:rate=30 -c:v h264_videotoolbox -color_range jpeg -pix_fmt nv12 -t 5 output.mp4

Confirmed on Macbook with Intel Core M CPU ; integrated GPU.

ffmpeg 3.4.1 built on 2017-12-11

#6906 fixed Re-order options for testsrc family of filters in manual Misaki
Description

According to the manual, option four for filter 'color' should be sample aspect ratio: https://ffmpeg.org/ffmpeg-filters.html

However, the command ffmpeg -filter_complex "color=white:160x160:1:1:10" output.mp4 produces output of 1 frame.

#6905 needs_more_info When copying video from .avi to .mp4, frames have incorrect pts values Misaki
Description

Step 1, generate a video with numbered frames:

ffmpeg -filter_complex "color=white:160x160:1,drawtext='fontcolor=black:fontsize=96:x=(W-tw)/2+4:y=(H-th)/2+4:text=%{n}:alpha=0.5',boxblur,drawtext='fontcolor=black:fontsize=96:x=(W-tw)/2:y=(H-th)/2:text=%{n}'" -preset veryslow -refs 8 -aq-strength 0.5 -threads 1 -crf 20 -frames:v 30 -movflags faststart ordered-frames.mp4

Step 2, convert it to avi:

ffmpeg -i ordered-frames.mp4 -c copy ordered-frames.avi

Step 3, convert back to mp4:

ffmpeg -i ordered-frames.avi -c copy -movflags faststart ordered-frames-avicopy.mp4

Examine the frames using ffprobe:

ffprobe -hide_banner -show_entries frame=pkt_pts_time,pkt_dts_time,pkt_size,coded_picture_number ordered-frames.mp4 -select_streams v | less

In another terminal tab, compare the new mp4:

ffprobe -hide_banner -show_entries frame=pkt_pts_time,pkt_dts_time,pkt_size,coded_picture_number ordered-frames-avicopy.mp4 -select_streams v | less

The pkt_dts_time values are just two more than the original file, but the pts values are now completely different. They are the packet dts values, which are different from the frame's pkt_dts values. This can be seen by looking at the packets and looking for similar sizes:

ffprobe -hide_banner -show_entries packet=pts_time,dts_time,size ordered-frames-avicopy.mp4 -select_streams v | less

Could also make arrays and by doing so sort everything by size so you wouldn't have to search to compare packets to frames, but it's easy to look for two or three packets.

Most programs seem to effectively ignore the pts for a frame shown by ffprobe, because they pay attention to the dts for a frame, which is different from the packet dts but usually the same as the frame pts and the packet pts.

So the 'bugged' mp4 files, copied from avi, appear to have a delay of a couple frames at most at the start, but then play normally with maybe a slight audio-video sync mismatch.

But it appears that the Chrome browser and Chrome OS's video player do care about the pts values, because they read the frames earlier than the dts values. This results in stuttering output: https://bugs.chromium.org/p/chromium/issues/detail?id=793635

They stutter the same way with the original avi file. This is probably unrelated to any ffmpeg libraries, but it does seem possible to make the copied mp4 files have better timestamps and so play correctly in Chrome.

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