TicketQuery should support order, group

[Markus Tacker <m@…>]

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

[sid]

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

[cboos]

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

[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

[cboos]

Support for grouping added in r5463.

[Markus Tacker <m@…>]

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

[cboos]

Well, it seems to work here:

---

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

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

---

Can you be more explicit about the TicketQuery which failed?

Also, does that happen with 0.11.3 as well?

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

[rblank]

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.