Opened 16 years ago
Last modified 4 years ago
#7419 new enhancement
Custom ticket status: customised ordering of statuses — at Version 8
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | next-major-releases |
Component: | ticket system | Version: | 0.11-stable |
Severity: | normal | Keywords: | |
Cc: | jevans591@…, jrioux@…, olya@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
We have a large number of custom ticket statuses now, thanks to 0.11 - it would be nice if I could define a sort order in the config file (similar to how you can do so in a [milestone-groups] section) so that when ordering tickets by status, they appear in my defined order.
Change History (8)
comment:1 by , 16 years ago
comment:3 by , 15 years ago
Cc: | added |
---|
comment:4 by , 15 years ago
Milestone: | 0.12 → next-major-0.1X |
---|
comment:5 by , 14 years ago
I'd like to note my support for this feature too; currently we run a simple four-step process (new, assigned, testing, closed), and it kind of sucks that viewing tickets by status displays them in alphabetical order.
Alternately, if I could specify the sort order in a query itself, I'd be more than satisfied with that; query?status=new&status=assigned&status=testing&status=closed&group=status
should IMO respect the order I'm setting within the query.
comment:6 by , 13 years ago
WORK-AROUND:
A simple work around is to rename your state names to have a number in front of them (e.g., 1 - Assigned
), although information on this section on the workflow wiki page implies it is best to leave new
and closed
alone. This doesn't really help the previous poster out when they only have 4 states for only assigned
and testing
can be thus renamed.
By the way, consider this my vote for this feature too.
comment:7 by , 13 years ago
Cc: | added |
---|
comment:8 by , 12 years ago
Description: | modified (diff) |
---|
#7489 closed as duplicate.