Edgewall Software
Modify

Opened 17 years ago

Closed 13 years ago

#2502 closed enhancement (fixed)

TicketQuery should support order, group

Reported by: Markus Tacker <m@…> Owned by: Jonas Borgström
Priority: normal Milestone: 0.11
Component: report system Version: 0.11-stable
Severity: normal Keywords: query needinfo
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

It would be nice to use &order=priority or &group=milestone with the TicketQuery wiki macro.

Attachments (0)

Change History (9)

comment:1 by sid, 16 years ago

Resolution: worksforme
Status: newclosed

Both ordering and group do work now in the TicketQuery wiki macro. It is not clear that the grouping is happening because there is no separation on the list, but it is working. Try these for example. Normal output for this:

[[TicketQuery(milestone=0.5,compact)]]

is:

#64, #66, #69, #70, #71

And grouping is:

[[TicketQuery(milestone=0.5&group=component,compact)]]

general #64,​70, search system #71, version control/changeset view #66, wiki system #69

And ordering is:

[[TicketQuery(milestone=0.5&order=owner,compact)]]

#64, #66, #69, #70, #71

comment:2 by Christian Boos, 16 years ago

Milestone: 0.11
Resolution: worksforme
Severity: normalminor
Status: closedreopened

The grouping is quite obvious when the table format is used. However, it might be a good idea to visualize them in compact mode too:

[[TicketQuery(milestone=0.5&group=component,compact)]]

would be: #66, #64,72,1125,70,1147,1258,1432,1217, #71, #69, using the upcoming support for list of tickets in TracLinks (see #3011).

in reply to:  1 comment:3 by ilias@…, 16 years ago

Replying to sid:

Both ordering and group do work now in the TicketQuery wiki macro.

related tickets: #4158, #4174

additionally, you can use the dynamic "$USER" variable, too: #3967

comment:4 by Christian Boos, 15 years ago

Resolution: fixed
Severity: minornormal
Status: reopenedclosed

Support for grouping added in r5463.

comment:5 by Christian Boos, 15 years ago

Component: wikireport system
Keywords: query added

comment:6 by Markus Tacker <m@…>, 13 years ago

Resolution: fixed
Status: closedreopened
Version: devel0.11-stable

In 0.11stable-r7716 order=priority has no effect.

comment:7 by Christian Boos, 13 years ago

Keywords: needinfo added

Well, it seems to work here:


 - [[TicketQuery(milestone=0.5,order=priority,compact)]]
 - [[TicketQuery(milestone=0.5,order=priority,desc=1,compact)]]

Can you be more explicit about the TicketQuery which failed?

Also, does that happen with 0.11.3 as well?

comment:8 by Markus Tacker <m@…>, 13 years ago

It's the querystring format that fails:

[[TicketQuery(status=accepted&status=assigned&status=new&status=reopened&order=priority&type=task)]]

where this works as expected.

[[TicketQuery(status=accepted|assigned|new|reopened,order=priority,type=task)]]

Could not test on 0.11.3, yet.

in reply to:  8 comment:9 by Remy Blank, 13 years ago

Resolution: fixed
Status: reopenedclosed

Replying to Markus Tacker <m@…>:

It's the querystring format that fails:

Oh, that's normal: query string syntax is not supported by the TicketQuery macro. You must use the query language.

It could probably be enhanced to support both syntaxes, though. Feel free to open a new enhancement request (after making sure that it hasn't been requested before) if you feel that this is a serious limitation.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Jonas Borgström to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.