Modify ↓
#9293 closed defect (fixed)
TicketQuery: order=priority => desc has no effect
| Reported by: | Owned by: | Remy Blank | |
|---|---|---|---|
| Priority: | low | Milestone: | 0.12 |
| Component: | ticket system | Version: | 0.11.6 |
| Severity: | minor | Keywords: | |
| Cc: | ondrej.kotaba@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
In wiki, in the following TicketQuery, the desc=0 and desc=1 make no difference, being always sorted as Trivial-first.
[[TicketQuery(max=50, status!=closed, milestone=Alpha, group=status, order=priority, desc=0, format=table, col=id|priority|summary|owner|status)]] [[TicketQuery(max=50, status!=closed, milestone=Alpha, group=status, order=priority, desc=1, format=table, col=id|priority|summary|owner|status)]]
Clicking the column to change the sort order links to a report where it works fine.
Attachments (0)
Change History (2)
comment:1 by , 15 years ago
| Milestone: | → 0.12 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:2 by , 15 years ago
| Component: | wiki system → ticket system |
|---|---|
| Owner: | set to |
Note:
See TracTickets
for help on using tickets.
Confirmed: the mere presence of
desc=was taken as "sort descending`. Fixed in [9619] by actually evaluating the argument.