NSIS-ka
A free C++ implementation of NSIS protocols

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.

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

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. This also allows displaying the link and description of a single ticket:

[[TicketQuery(id=123)]]

This is displayed as:

#123
Refreshing/MA re-use Response via MA and w/o Stack Proposal causes MA re-use failure

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:

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#175 fixed Confirm carries wrong NLI after re-routing happened bless bless@…
Description

Confirm is rejected due to wrong Responder Cookie. This was probably introduced by r6683.

#174 fixed Mutex lock error in routingtable::failure_ind_ma() bless bless@…
Description
2012-07-06 10:28:25.746-4059- EVENT /4: TPoverTCP       stop_receiver_thread() - Receiver thread <140471258998528> signaled for termination
2012-07-06 10:28:28.554-4059- EVENT /8: TPoverTCP       receiver - Thread <140471258998528> found terminate signal after poll
2012-07-06 10:28:28.554-4059- EVENT /2: TPoverTCP       receiver - Poll hung up
2012-07-06 10:28:28.554-4059- DEBUG /4: TPoverTCP       receiver - Other side ([IPv4-mapped address]: ::ffff:10.16.18.16:42846, tcp) closed connection for socket 12
2012-07-06 10:28:28.554-4059- DEBUG /4: TPoverTCP       bytes_received-common_header_length=4294967288 msgcontentlength: 0
2012-07-06 10:28:28.554-4059- DEBUG /4: TPoverTCP       receiver - Thread <140471258998528> shutting down and closing socket [IPv4-mapped address]: ::ffff:10.16.18.16:42846, tcp
2012-07-06 10:28:28.554-4059- DEBUG /4: TPoverTCP       receiver - Thread <140471258998528> terminated
2012-07-06 10:28:28.554-4059- DEBUG /4: TPoverTCP       receiver - Signaling main loop for cleanup
2012-07-06 10:28:28.554-4059- EVENT /4: TPoverTCP       terminate()   - got request to shutdown connection for peer 0x7fc2100070b0
2012-07-06 10:28:28.554-4059- EVENT /4: TPoverTCP       terminate()   - connection for peer 0x7fc2100070b0 is already in mode shutdown
2012-07-06 10:28:28.554-4059- DEBUG /4: TPoverTCP       Got cleanup request for thread <140471258998528>
2012-07-06 10:28:28.554-4059- EVENT /4: TPoverTCP       cleanup_receiver_thread() - Receiver thread <140471258998528> is terminated
2012-07-06 10:28:28.554-4059- DEBUG /4: TPoverTCP       cleanup_receiver_thread() - Cleanup receiver thread <140471258998528>. Done.
2012-07-06 10:28:28.554-4059- EVENT /4: TPoverTCP       senderthread - <140471250605824> terminated connection.
2012-07-06 10:28:28.554-4059- DEBUG /4: GIST Signaling  Received incoming message #1306 on Queue
2012-07-06 10:28:28.554-4059- DEBUG /4: GIST Signaling  process_tp_msg() - received message #1306 from TP
2012-07-06 10:28:28.554-4059**ERROR**4: GIST Signaling  Received error Other side closed connection from TransportProtocol peer [IPv4-mapped address]: ::ffff:10.18.19.19:30000, tcp
2012-07-06 10:28:28.554-4059- DEBUG /4: GIST Routing    Got a failure indication for this MA (er_MAfailure), must iterate MA table to find it's entry
2012-07-06 10:28:28.554-4059- DEBUG /4: GIST Signaling  Received incoming message #1306 from TP Module
2012-07-06 10:28:28.554-4059- DEBUG /4: GIST Signaling  Received incoming message #1309 on Queue
2012-07-06 10:28:28.554-4059- DEBUG /4: GIST Signaling  process_tp_msg() - received message #1309 from TP
2012-07-06 10:28:28.554-4059**ERROR**4: GIST Signaling  Received error Other side closed connection from TransportProtocol peer [IPv4-mapped address]: ::ffff:10.16.18.16:42846, tcp
2012-07-06 10:28:28.554-4059- DEBUG /4: GIST Routing    Got a failure indication for this MA (er_MAfailure), must iterate MA table to find it's entry
2012-07-06 10:28:28.554-4059**ERROR**2: routingtable::locktable() Mutex Lock failed. Error: Success
2012-07-06 10:28:28.554-4059- DEBUG /4: GIST Signaling  Received incoming message #1309 from TP Module
2012-07-06 10:31:00.481-4059- DEBUG /8: TimerModule     sent reply mid 1262 for elapsed timer 148 to Coordination (ext)
2012-07-06 10:31:00.481-4059- DEBUG /8: TimerModule     got 1 elapsed timer(s)

#173 fixed routing state and MA handling of nodes with different i/f addresses bless bless@…
Description

Case: Node sends Query downstream, next peer answers with a response via an already existing MA. The code fails to handle the case where a node reports a different i/f in the NLI, that doesn't match the used MAs i/f.

2012-07-04 15:06:16.888-1658- DEBUG /4: GIST Signaling  Sending from: 10.18.19.18
2012-07-04 15:06:16.888-1658- DEBUG /4: GIST Signaling  Sending <query> sid: 10000000-10000000-10000000-10000000 to [IP address]: 10.19.20.20:270, UNKNOWN
2012-07-04 15:06:16.888-1658- EVENT /4: GIST Signaling  Sending (msg#583):
<query>:   NSLP ID: 3

Message Routing Information <mri_pathcoupled>: (Mandatory)
MRM-ID                : 0
IP-Version            : 4
Flags:                : 
Source Address        : 10.15.16.15
Destination Address   : 10.19.20.20
Source Prefixlen      : 32
Destination Prefixlen : 32
Direction             : Downstream

SessionID <sessionid>: 10000000-10000000-10000000-10000000

NLI <nli>: (0)

IP_TTL: 10
IP_Version: 4
RS-Validity-Time: 30000
PI length: 16
PI: ca5bdd4eafc08b3629dd8400f89638d0 (.[.N...6).....8.)
IF_Address: 10.18.19.18

   Query Cookie : <0xd47b1962>

   StackProposal
Profiles: 2
1 MA fields: <1> 
2 MA fields: <2> <1> 

   StackConfigurationData
Profiles: 2
MA-Hold Time: 180000 ms
Protocol: 1 Profile: 1 Option Data: <empty>
Protocol: 1 Profile: 2 Option Data: <empty>

2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu        calculated PDU size of: 124
2012-07-04 15:06:16.888-1658- DEBUG /8: NTLPprotocol    starting to serialize
2012-07-04 15:06:16.888-1658- DEBUG /8: NTLPprotocol    prepended magic number 4e04bda5
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu        calculated PDU size of: 124
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu        ntlp_pdu::serialize: query expected pdulen:124
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu:: serialize processing mri_pathcoupled
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu:: serialize wrote mri_pathcoupled@pos: 12 length:20
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu:: serialize processing sessionid
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu:: serialize wrote sessionid@pos: 32 length:20
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu:: serialize processing nli
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu:: serialize wrote nli@pos: 52 length:32
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu:: serialize processing querycookie
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu:: serialize wrote querycookie@pos: 84 length:8
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu:: serialize processing stackprop
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu:: serialize wrote stackprop@pos: 92 length:16
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu:: serialize processing stack_conf_data
2012-07-04 15:06:16.888-1658- DEBUG /4: NTLP_pdu:: serialize wrote stack_conf_data@pos: 108 length:20
2012-07-04 15:06:16.888-1658- DEBUG /8: NTLPprotocol    PDU serialized.
2012-07-04 15:06:16.888-1658- EVENT /4: GIST Signaling  Sending msg to Protocol #255 (UNKNOWN) Dest:::ffff:10.19.20.20
2012-07-04 15:06:16.888-1658- DEBUG /4: TPqueryEncap    Setting IP hop limit to 10
2012-07-04 15:06:16.888-1658- DEBUG /4: TPqueryEncap    Setting IP RAO to 0
2012-07-04 15:06:16.888-1658- DEBUG /4: protlib::util::set_ancillary_data() Adding IP ROA 0
2012-07-04 15:06:16.888-1658- DEBUG /4: protlib::util::set_ancillary_data() Adding IP hop limit 10
2012-07-04 15:06:16.888-1658- DEBUG /4: protlib::util::set_ancillary_data() Adding outgoing IP address 10.18.19.18
2012-07-04 15:06:16.888-1658- EVENT /4: TPqueryEncap     sender: >>----Sent---->> message (128 bytes) using socket 3 to [IPv4-mapped address]: ::ffff:10.19.20.20:270, UNKNOWN-07-04 15:06:16.888-1658- DEBUG /4: GIST Processing Query sent to Request C-Mode setup
2012-07-04 15:06:16.888-1658- EVENT /8: TimerModule     Timer 82 (0s 500ms) started for Coordination (ext) with mid 584
2012-07-04 15:06:16.888-1658- DEBUG /4: GIST Processing Started timer: NO_RESPONSE 500 ms mid 584
2012-07-04 15:06:16.888-1658- EVENT /8: TimerModule     Timer 83 (2s 0ms) started for Coordination (ext) with mid 585
2012-07-04 15:06:16.888-1658- DEBUG /4: GIST Processing Started timer: QUEUE_POLL 2000 ms mid 585
2012-07-04 15:06:16.888-1658- EVENT /4: GIST Processing Enqueued data for later sending. Count of enqueued data for this target: 1
2012-07-04 15:06:16.888-1658- DEBUG /4: GIST Routing    ******* Unlocking Session-ID 10000000-10000000-10000000-10000000 with state QN_AWAITING_RESPONSE
2012-07-04 15:06:16.890-1658- EVENT /8: TPoverTCP       receiver - <<--Received--<< packet (120 bytes) at socket 13 from [IPv4-mapped address]: ::ffff:10.18.19.19:30000, tcp2-07-04 15:06:16.890-1658- DEBUG /4: TPoverTCP       bytes_received-common_header_length=112 msgcontentlength: 112
2012-07-04 15:06:16.890-1658- DEBUG /4: TPoverTCP       receiver - receipt of PDU now complete, sending msg#586 to module Signaling
2012-07-04 15:06:16.890-1658- DEBUG /4: GIST Signaling  Received incoming message #586 on Queue
2012-07-04 15:06:16.890-1658- DEBUG /4: GIST Signaling  process_tp_msg() - received message #586 from TP
2012-07-04 15:06:16.890-1658- DEBUG /4: GIST Signaling  process_tp_msg() - received PDU (transport: TPoverTCP) now parsing...
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_IE         started to deserialize known_ntlp_pdu @pos:0 bytes left in buffer:120
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_IE         started to deserialize known_ntlp_object @pos:8 bytes left in buffer:112
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_object     ntlp_object::decodeheader, special class MRI encountered, set subtype: 0
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_IE         IEManager::deserialize_known_ntlp_object: found object type 0@pos:8, total object length (incl. header):20
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_object     ntlp_object::decodeheader, special class MRI encountered, set subtype: 0
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_pdu        ntlp_pdu: inserted known object (mri_pathcoupled) of 20 bytes to designated position 0
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_IE         started to deserialize known_ntlp_object @pos:28 bytes left in buffer:92
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_IE         IEManager::deserialize_known_ntlp_object: found object type 1@pos:28, total object length (incl. header):20
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_pdu        ntlp_pdu: inserted known object (sessionid) of 20 bytes to designated position 1
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_IE         started to deserialize known_ntlp_object @pos:48 bytes left in buffer:72
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_IE         IEManager::deserialize_known_ntlp_object: found object type 2@pos:48, total object length (incl. header):32
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_pdu        ntlp_pdu: inserted known object (nli) of 32 bytes to designated position 2
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_IE         started to deserialize known_ntlp_object @pos:80 bytes left in buffer:40
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_IE         IEManager::deserialize_known_ntlp_object: found object type 5@pos:80, total object length (incl. header):8
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_pdu        ntlp_pdu: inserted known object (querycookie) of 8 bytes to designated position 3
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_IE         started to deserialize known_ntlp_object @pos:88 bytes left in buffer:32
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_IE         IEManager::deserialize_known_ntlp_object: found object type 6@pos:88, total object length (incl. header):32
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_pdu        ntlp_pdu: inserted known object (respcookie) of 32 bytes to designated position 4
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP_pdu        calculated PDU size of: 120
2012-07-04 15:06:16.890-1658- DEBUG /4: NTLP pdu        Check for correct Message Length passed. Simple message integrity is OK.
2012-07-04 15:06:16.890-1658- DEBUG /8: NTLPprotocol    process_tp_recv_msg(): deserialization completed (read 120 bytes).
2012-07-04 15:06:16.890-1658- DEBUG /4: GIST Signaling  process_tp_msg() - parsed PDU 
2012-07-04 15:06:16.891-1658- DEBUG /4: GIST Signaling  Incoming message is addressed to NSLP ID 3
2012-07-04 15:06:16.891-1658- DEBUG /4: NSLPtable       Successfully looked up API caller address for NSLPID 3
2012-07-04 15:06:16.891-1658- DEBUG /4: NSLPtable       Successfully looked up API caller address for NSLPID 3
2012-07-04 15:06:16.891-1658- DEBUG /4: GIST Signaling  Accepted incoming message, it is addressed to NSLP ID 3 at API interface 21
2012-07-04 15:06:16.891-1658- DEBUG /4: GIST Signaling  Passing response msg#588 to coordination
2012-07-04 15:06:16.891-1658- DEBUG /4: GIST Signaling  Received incoming message #586 from TP Module
2012-07-04 15:06:16.891-1658- EVENT /4: GIST Processing Received message #588 (SigInd) from: Signaling, peer: ::ffff:10.18.19.19, PDU: 
<response>:   NSLP ID: 3

Message Routing Information <mri_pathcoupled>: (Mandatory)
MRM-ID                : 0
IP-Version            : 4
Flags:                : D
Source Address        : 10.15.16.15
Destination Address   : 10.19.20.20
Source Prefixlen      : 32
Destination Prefixlen : 32
Direction             : Upstream

SessionID <sessionid>: 10000000-10000000-10000000-10000000

NLI <nli>: (0)

IP_TTL: 0
IP_Version: 4
RS-Validity-Time: 30000
PI length: 16
PI: 25b75eee815728078bd20d4d47219977 (%.^..W(....MG!.w)
IF_Address: 10.17.19.19

   Query Cookie : <0xd47b1962>

   Responder Cookie : <0x05353977000400006e92d68dc9989a4a8286c3ebe8e37b07d92e5343>

2012-07-04 15:06:16.891-1658- DEBUG /4: GIST Processing Received <response> sid: 10000000-10000000-10000000-10000000 from [IPv4-mapped address]: ::ffff:10.18.19.19:30000, tcp
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Processing No NATed GIST PDU, taking original MRI of the PDU
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Routing    Active Routing Entries: 2 MAs: 3 SII handles: 3
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Routing    ******* Returning entry for Session-ID 10000000-10000000-10000000-10000000 with state QN_AWAITING_RESPONSE
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Routing    There is no active Message Association to maintain
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Processing Evaluating current routing state
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Processing GIST Response received, inspecting (QN Awaiting Response)
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Processing Query Cookie matched, accepting
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Processing Installed NLI in routing state, SII handle = 4
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Processing Installed peer's RS-Validity time of 30000ms
2012-07-04 15:06:16.892-1658- EVENT /8: TimerModule     Timer 84 (0s 30000ms) started for Coordination (ext) with mid 589
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Processing Started timer: INACTIVE_Q_NODE 30000 ms mid 589
2012-07-04 15:06:16.892-1658- DEBUG /4: TimerModule     Stopped timer 82, mid 584 for Coordination (ext)
2012-07-04 15:06:16.892-1658- EVENT /8: TimerModule     Timer 85 (0s 12517ms) started for Coordination (ext) with mid 591
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Processing Started timer: REFRESH_Q_NODE 12517 ms mid 591
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Processing Sending back confirm in C-Mode
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Routing    MA not foundfor NLI 25b75eee815728078bd20d4d47219977 (%.^..W(....MG!.w), IP:10.17.19.19
2012-07-04 15:06:16.892-1658**ERROR**2: GIST Processing No existing MA found and no Stack proposal/config given, cannot figure out where to send Confirm in C-Mode. This is probably an internal error.
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Processing Error Message Sender called
2012-07-04 15:06:16.892-1658**ERROR**2: GIST Processing ERROR_GIST_MISSING_OBJECT
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Processing IP Source IS last GIST hop, sending to it.
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Signaling  Received incoming message #593 on Queue
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Signaling  Sending from: 10.18.19.18
2012-07-04 15:06:16.892-1658- DEBUG /4: GIST Signaling  Sending <error> sid: N/A to [IP address]: 10.17.19.19:270, udp
2012-07-04 15:06:16.892-1658- EVENT /4: GIST Signaling  Sending (msg#593):
<error>:
NLI <nli>: (0)

IP_TTL: 0
IP_Version: 4
RS-Validity-Time: 30000
PI length: 16
PI: ca5bdd4eafc08b3629dd8400f89638d0 (.[.N...6).....8.)
IF_Address: 10.18.19.18

   Error Data
ProtocolError(2): Object Type Error / Missing Object (9/2)
Common header: ver=1 hops=0 length=0 nslpID=3 type=1 flags=SM-D- (c0)
10000000-10000000-10000000-10000000
MRI-Length:   10
Embedded MRI: <mri_pathcoupled>: (Mandatory)
MRM-ID                : 0
IP-Version            : 4
Flags:                : D
Source Address        : 10.15.16.15
Destination Address   : 10.19.20.20
Source Prefixlen      : 20
Destination Prefixlen : 20
Direction             : Upstream

Number of additional info objects: 1
Message length info:0
MTU info:0
Object Type info:3

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

Last modified 2 years ago Last modified on Jul 9, 2015, 8:37:14 AM