Edgewall Software
Modify

Opened 9 years ago

Closed 5 years ago

#2502 closed enhancement (fixed)

TicketQuery should support order, group

Reported by: Markus Tacker <m@…> Owned by: jonas
Priority: normal Milestone: 0.11
Component: report system Version: 0.11-stable
Severity: normal Keywords: query needinfo
Cc:
Release Notes:
API 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 follow-up: Changed 8 years ago by sid

  • Resolution set to worksforme
  • Status changed from new to closed

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 Changed 8 years ago by cboos

  • Milestone set to 0.11
  • Resolution worksforme deleted
  • Severity changed from normal to minor
  • Status changed from closed to reopened

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

comment:3 in reply to: ↑ 1 Changed 8 years ago by ilias@…

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 Changed 7 years ago by cboos

  • Resolution set to fixed
  • Severity changed from minor to normal
  • Status changed from reopened to closed

Support for grouping added in r5463.

comment:5 Changed 7 years ago by cboos

  • Component changed from wiki to report system
  • Keywords query added

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

  • Resolution fixed deleted
  • Status changed from closed to reopened
  • Version changed from devel to 0.11-stable

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

comment:7 Changed 6 years ago by cboos

  • 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 follow-up: Changed 5 years ago by Markus Tacker <m@…>

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.

comment:9 in reply to: ↑ 8 Changed 5 years ago by rblank

  • Resolution set to fixed
  • Status changed from reopened to closed

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.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed The owner will remain jonas.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from jonas to the specified user.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.