Modify ↓
Ticket #5031 (new enhancement)
Opened 5 years ago
Last modified 2 years ago
Queries ought to support less/great than for ordered values (i.e. priorities and severities)
| Reported by: | macke@… | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-0.1X |
| Component: | ticket system | Version: | 0.10.2 |
| Severity: | normal | Keywords: | query |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
I.e. expand the [is|is not] operator set a bit.
Attachments
Change History
comment:1 follow-up: ↓ 2 Changed 5 years ago by cboos
- Keywords query added
- Milestone set to 0.12
- Severity changed from trivial to normal
comment:2 in reply to: ↑ 1 Changed 5 years ago by Marcus Lindblom <macke@…>
Replying to cboos:
Similar to the request for ordering on dates (I can't find that ticket anymore, but it's not a duplicate anyway).
Right.
And no, it's not a trivial change...
Sorry, I meant priority. Shouldn't have touched that field.
The TicketQuery expressions should also support the common ordering operators (<, <=, =>, >).
Yup.
comment:3 Changed 5 years ago by cboos
#1943 was the ticket about ticket date range queries I was looking for this morning.
comment:4 Changed 5 years ago by cboos
comment:5 Changed 4 years ago by cboos
- Milestone changed from 0.13 to 0.12
comment:6 Changed 3 years ago by rblank
Related to #7419, which suggests defining an order for ticket statuses.
comment:7 Changed 2 years ago by cboos
- Owner jonas deleted
comment:8 Changed 2 years ago by rblank
- Milestone changed from 0.12 to next-major-0.1X
Note: See
TracTickets for help on using
tickets.
Similar to the request for ordering on dates (I can't find that ticket anymore, but it's not a duplicate anyway).
And no, it's not a trivial change...
The TicketQuery expressions should also support the common ordering operators (<, <=, =>, >).