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: 1 [[TicketQuery(status=new&milestone=,count)]]
Number of new tickets: 1021 [[TicketQuery(status=new,count)]]
Number of reopened tickets: 47 [[TicketQuery(status=reopened,count)]]
Number of assigned tickets: 21 [[TicketQuery(status=assigned,count)]]
Number of invalid tickets: 178 [[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets: 171 [[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets: 128 [[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets: 214 [[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets: 2240 [[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset): 1 [[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets: 4023 [[TicketQuery(count)]]
Number of tickets reported or owned by current user: 0 [[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: #3697, #2268, #3348 [[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 grass-dev@… neteler
Summary g.setproj bug: latitude_of_center and longitude_of_center ignored

Format: list

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

This is displayed as:

No results

[[TicketQuery(id=123)]]

This is displayed as:

#123
r.in.xyz: import bug when using scanned extent

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:

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#4023 fixed TypeError: a bytes-like object is required, not 'str' grass-dev@… pvanbosgeo
#4022 fixed impossible to remove vect and delete attribute from gui grass-dev@… 1266
#4021 fixed r.import/v.import: confusing error message "ERROR: proj" grass-dev@… neteler
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 2934)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#4023 fixed TypeError: a bytes-like object is required, not 'str' grass-dev@… pvanbosgeo
Description

Running the addon r.diversity on grass 7.9 (Windows 10), I get the following error:

C:\Users\hsc\Documents\GRASSGIS\scripts\r.diversity.py --overwrite input=landschap@datamodel prefix=renyi3 alpha=0.6 method=renyi
Traceback (most recent call last):
  File
"C:\Users\hsc\Documents\GRASSGIS\scripts\r.diversity.py",
line 283, in <module>
    sys.exit(main())
  File
"C:\Users\hsc\Documents\GRASSGIS\scripts\r.diversity.py",
line 149, in main
    quiet, overwrite)
  File
"C:\Users\hsc\Documents\GRASSGIS\scripts\r.diversity.py",
line 160, in calculateM
    createConfFile(r, map_in, home)
  File
"C:\Users\hsc\Documents\GRASSGIS\scripts\r.diversity.py",
line 240, in createConfFile
    fileConf.writelines(outputLine)
TypeError: a bytes-like object is required, not 'str'
(Wed Jan 22 12:02:17 2020) Command finished (3 sec)    

I guess something to do with Python2 vs Python 3 (using the latter), but I can't pin it down.

#4022 fixed impossible to remove vect and delete attribute from gui grass-dev@… 1266
Description

I cannot remove vector object and/or attribute data from the right-clic menu on attribute box in the gui (delete selected records/features) with grass 7.8 or 7.9 (on debian buster with 'fr' or 'en' locale)

But "v.edit tool=delete map=mymap where="mycolum=myvalue" and db.execute "sql=DELETE FROM mymap WHERE mycolomn = myvalue" work fine.

console return : Traceback (most recent call last):

File "/usr/local/grass78/gui/wxpython/dbmgr/base.py", line

1997, in OnDeleteSelected

if self.OnDataItemDelete(None) and self.mapdisplay:

File "/usr/local/grass78/gui/wxpython/dbmgr/base.py", line

1748, in OnDataItemDelete

self.ApplyCommands(self.listOfCommands, self.listOfSQLStatements)

File "/usr/local/grass78/gui/wxpython/dbmgr/base.py", line

982, in ApplyCommands

sqlFile.write(sql.encode('utf-8') + ';') TypeError : can't concat str to bytes

#4021 fixed r.import/v.import: confusing error message "ERROR: proj" grass-dev@… neteler
Description

For most users the "ERROR: proj" part in the notification which CRS was found and that the reprojection does not match that of the current location is confusing, also in a technical sense as it is sent to stderr:

grass78 ~/grassdata/nc_spm_08/user1

# generate test data
v.out.ogr input=roadsmajor output=roadsmajor.gpkg
ogr2ogr -t_srs epsg:4326 roadsmajor_LL.gpkg roadsmajor.gpkg

v.import input=roadsmajor_LL.gpkg output=test --o
WARNING: Projection of dataset does not appear to match current location.

         Location PROJ_INFO is:
         name: Lambert Conformal Conic
         proj: lcc
         datum: nad83
         a: 6378137.0
         es: 0.006694380022900787
         lat_1: 36.16666666666666
         lat_2: 34.33333333333334
         lat_0: 33.75
         lon_0: -79
         x_0: 609601.22
         y_0: 0
         no_defs: defined
         init: EPSG:3358

         Dataset PROJ_INFO is:
         name: WGS 84
         datum: wgs84
         ellps: wgs84
         proj: ll
         no_defs: defined

         ERROR: proj                          <=== ?!
Importing <roadsmajor_LL.gpkg> ...
Check if OGR layer <roadsmajor> contains polygons...
 100%
Creating attribute table for layer <roadsmajor>...
Default driver / database set to:
driver: sqlite
database: $GISDBASE/$LOCATION_NAME/$MAPSET/sqlite/sqlite.db
Column name <cat> renamed to <cat_>
Importing 355 features (OGR layer <roadsmajor>)...
 100%
-----------------------------------------------------
Building topology for vector map <test@PERMANENT>...
Registering primitives...
Reprojecting <test>...
WARNING: Vector map <test> already exists and will be overwritten
Reprojecting primitives ...
Building topology for vector map <test@user1>...
Registering primitives...

Hence, "ERROR" followed by "Importing..." is not ideal.

I didn't get yet an idea since the message is composed in r.in.gdal/v.in.ogr:

https://github.com/OSGeo/grass/blob/master/raster/r.in.gdal/proj.c#L196

Effectively, the "ERROR" part should be suppressed when r.in.gdal was called by r.import (v.in.ogr respectively).

Any ideas?

1 2 3 4 5 6 7 8 9 10 11


See also: TracQuery, TracTickets, TracReports

Last modified 9 days ago Last modified on May 8, 2022, 3:11:36 PM
Note: See TracWiki for help on using the wiki.