wiki:TicketQuery

TicketQuery Wiki Macro

The TicketQuery macro lets you display ticket information anywhere that accepts WikiFormatting. The query language used by the [[TicketQuery]] macro is described in the TracQuery page.

Usage

[[TicketQuery]]

Wiki macro listing tickets that match certain criteria.

This macro accepts a comma-separated list of keyed parameters, in the form "key=value".

If the key is the name of a field, the value must use the syntax of a filter specifier as defined in TracQuery#QueryLanguage. Note that this is not the same as the simplified URL syntax used for query: links starting with a ? character. Commas (,) can be included in field values by escaping them with a backslash (\).

Groups of field constraints to be OR-ed together can be separated by a literal or argument.

In addition to filters, several other named parameters can be used to control how the results are presented. All of them are optional.

The format parameter determines how the list of tickets is presented:

  • list -- the default presentation is to list the ticket ID next to the summary, with each ticket on a separate line.
  • compact -- the tickets are presented as a comma-separated list of ticket IDs.
  • count -- only the count of matching tickets is displayed
  • rawcount -- only the count of matching tickets is displayed, not even with a link to the corresponding query (since 1.1.1)
  • table -- a view similar to the custom query view (but without the controls)
  • progress -- a view similar to the milestone progress bars

The max parameter can be used to limit the number of tickets shown (defaults to 0, i.e. no maximum).

The order parameter sets the field used for ordering tickets (defaults to id).

The desc parameter indicates whether the order of the tickets should be reversed (defaults to false).

The group parameter sets the field used for grouping tickets (defaults to not being set).

The groupdesc parameter indicates whether the natural display order of the groups should be reversed (defaults to false).

The verbose parameter can be set to a true value in order to get the description for the listed tickets. For table format only. deprecated in favor of the rows parameter

The rows parameter can be used to specify which field(s) should be viewed as a row, e.g. rows=description|summary

The col parameter can be used to specify which fields should be viewed as columns. For table format only.

For compatibility with Trac 0.10, if there's a last positional parameter given to the macro, it will be used to specify the format. Also, using "&" as a field separator still works (except for order) but is deprecated.

Examples

Example Result Macro
Number of Triage tickets: 14 [[TicketQuery(status=new&milestone=,count)]]
Number of new tickets: 14 [[TicketQuery(status=new,count)]]
Number of reopened tickets: 0 [[TicketQuery(status=reopened,count)]]
Number of assigned tickets: 0 [[TicketQuery(status=assigned,count)]]
Number of invalid tickets: 3 [[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets: 6 [[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets: 1 [[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets: 5 [[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets: 54 [[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset): 16 [[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets: 85 [[TicketQuery(count)]]
Number of tickets reported or owned by current user: 5 [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
Number of tickets created this month: 0 [[TicketQuery(created=thismonth..,count)]]
Number of closed Firefox tickets: 0 [[TicketQuery(status=closed,keywords~=firefox,count)]]
Number of closed Opera tickets: 0 [[TicketQuery(status=closed,keywords~=opera,count)]]
Number of closed tickets affecting Firefox and Opera: 0 [[TicketQuery(status=closed,keywords~=firefox opera,count)]]
Number of closed tickets affecting Firefox or Opera: 0 [[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
Number of tickets that affect Firefox or are closed and affect Opera: 0 [[TicketQuery(status=closed,keywords~=opera,or,keywords~=firefox,count)]]
Number of closed Firefox tickets that don't affect Opera: 0 [[TicketQuery(status=closed,keywords~=firefox -opera,count)]]
Last 3 modified tickets: #131, #37, #129 [[TicketQuery(max=3,order=modified,desc=1,compact)]]

Details of ticket #1:

[[TicketQuery(id=1,col=id|owner|reporter,rows=summary,table)]]

Ticket Owner Reporter
#1 weber weber
Summary Error message "Wrong observation epoch(s)"

Format: list

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

This is displayed as:

No results

[[TicketQuery(id=123)]]

This is displayed as:

#123
BKG caster does not actively close server connections

Format: compact

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

This is displayed as:

No results

Format: count

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

This is displayed as:

0

Format: progress

[[TicketQuery(milestone=0.12.8&group=type,format=progress)]]

This is displayed as:

defect

54 / 66

enhancement

9 / 11

task

6 / 8

Format: table

You can choose the columns displayed in the table format (format=table) using col=<field>. You can specify multiple fields and the order they are displayed 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 69)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#129 wontfix BNC with openssl1.1 on Debian 10 stuerze hx97177@…
#126 invalid BNC connecting to mountpoint, RINEX observations version 3, only L1 info stuerze anonymous
#121 worksforme Possible SYN flooding on port 2101 regina.operation@… regina.operation@…
1 2 3 4 5 6 7 8 9 10 11

Full rows

In table format you can specify full rows 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 69)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#129 wontfix BNC with openssl1.1 on Debian 10 stuerze hx97177@…
Description

Hello

I'm using bnc-2.12.9-ubuntu-64bit-shared on an Ubuntu server since many years.

Now I have to set up a new server with BNC. The new server is running Debian 10. I tried using bnc-2.12.18-debian8-64bit-static, but I'm getting the following error messages:

QSslSocket: cannot resolve CRYPTO_num_locks QSslSocket: cannot resolve CRYPTO_set_id_callback QSslSocket: cannot resolve CRYPTO_set_locking_callback QSslSocket: cannot resolve sk_free QSslSocket: cannot resolve sk_num QSslSocket: cannot resolve sk_pop_free QSslSocket: cannot resolve sk_value QSslSocket: cannot resolve SSL_library_init QSslSocket: cannot resolve SSL_load_error_strings QSslSocket: cannot resolve SSLv3_client_method QSslSocket: cannot resolve SSLv23_client_method QSslSocket: cannot resolve SSLv3_server_method QSslSocket: cannot resolve SSLv23_server_method QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf QSslSocket: cannot resolve SSLeay QSslSocket: cannot call unresolved function CRYPTO_num_locks QSslSocket: cannot call unresolved function CRYPTO_set_id_callback QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback QSslSocket: cannot call unresolved function SSL_library_init QSslSocket: cannot call unresolved function SSLv23_client_method QSslSocket: cannot call unresolved function sk_num QSslSocket: cannot call unresolved function SSLv23_client_method QSslSocket: cannot call unresolved function SSL_library_init

It seems that the problem is that the server has openssl version 1.1.1d. The old server e.g. has openssl 1.0.2g. Is the bnc software only working with openssl 1.0? I'm not allowed to downgrade the openssl version. Is there any other solution?

Many thanks for your help

#126 invalid BNC connecting to mountpoint, RINEX observations version 3, only L1 info stuerze anonymous
Description

Good morning. From Spain, connecting to mountpoint to obtain RINEX v3 file. I can see only L1 information, nothing about L2. Thank you

#121 worksforme Possible SYN flooding on port 2101 regina.operation@… regina.operation@…
Description

Hello,

A lot of client on our ntripcaster professional (version 2.031) observed a lot of disconnection during 20 minutes. On the different log of the ntripcaster we saw only many disconnections (but not all the connections, maybe 60% of disconnections). There is no more connections from clients or sources which let thinking to a saturation of the 2101 port. We thinking on an attack but the analyses done by the network team said that there was no attack. A system analysis was done also, but the différent limits wasn't reach by the system. So we suspect an issue on the ntripcaster, Have you ever seen this behavior ?

1 2 3 4 5 6 7 8 9 10 11


See also: TracQuery, TracTickets, TracReports

Last modified 4 months ago Last modified on Aug 3, 2021, 7:27:01 PM
Note: See TracWiki for help on using the wiki.