Edgewall Software
Modify

Opened 12 years ago

Last modified 5 years ago

#5031 new enhancement

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-releases
Component: ticket system Version: 0.10.2
Severity: normal Keywords: query
Cc: olemis+trac@…
Release Notes:
API Changes:

Description

I.e. expand the [is|is not] operator set a bit.

Attachments (0)

Change History (10)

comment:1 Changed 12 years ago by Christian Boos

Keywords: query added
Milestone: 0.12
Severity: trivialnormal

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 (<, ⇐, ⇒, >).

comment:2 in reply to:  1 Changed 12 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 12 years ago by Christian Boos

#1943 was the ticket about ticket date range queries I was looking for this morning.

comment:4 Changed 12 years ago by Christian Boos

(more precisely #4594, which was closed as a duplicate of #1943)

comment:5 Changed 10 years ago by Christian Boos

Milestone: 0.130.12

comment:6 Changed 10 years ago by Remy Blank

Related to #7419, which suggests defining an order for ticket statuses.

comment:7 Changed 9 years ago by Christian Boos

Owner: Jonas Borgström deleted

comment:8 Changed 9 years ago by Remy Blank

Milestone: 0.12next-major-0.1X

comment:9 Changed 5 years ago by trancesilken@…

The problem here is that the priority and severity and other such enum type of values are stored as text. Sorting them based on < > ⇐ ≥ is not an option unless one also compares against the ordering number which is stored in the enum table.

However, the ordering number does only reflect the ordering by which the individual items will be displayed in the drop down when editing an issue.

The information as to which priority has the highest priority and which has the lowest is simply not there, unless one wants to utilize the ordering field in the enum table for this. And by comparing the strings alphanumerically will not do the trick, unless you assign your priorities names such as "1" for the lowest priority, or "2", or "3" for the highest priority.

The same is true for the severity field.

comment:10 Changed 5 years ago by Olemis Lang <olemis+trac@…>

Cc: olemis+trac@… added

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set.
The owner will be changed from (none) to anonymous.

Add Comment


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