[#JRA-1142] Priority sorting not consistent with priority ordering

JIRA

Priority sorting not consistent with priority ordering

Created: 17/Jan/03 03:40 AM Updated: 30/Jul/06 07:36 PM

Component/s:

None

Affects Version/s:

2.0

Fix Version/s:

2.1 Pro, 2.1 Enterprise

Time Tracking:

Not Specified

Environment:

eap6

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-1647~~ Priorities not sorted in correct sequence

Reference

This issue relates to:

~~JRA-1148~~ Incorrect sort order on Issue Navigator

Participants:	Barry Kaplan, Edwin Wong [Atlassian], Jed Wesley-Smith and Scott Farquhar [Atlassian]
Since last comment:	5 years, 22 weeks, 1 day ago
Resolution Date:	07/May/03 03:16 AM
Labels:

Description

« Hide

I have been screwing around with the priorities (adding, removing, renaming, reordering). I'm now back to the default except with "trivial" renamed to "smell". But when click the on the priority in a table, medium is being sorted above high.

Looking at the database I see that priorty sequences seem to be correct (blocker 1.000 .. smell 5.000). But the sorting is consistent with the priorities ID column, which in my case is:

1 block
2 medium
5 high
6 low
7 smell

Also, the arrow in the column header points down when the higher priorities are at the top, and up when the lower priorities are at the top. Is the normal?

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Scott Farquhar [Atlassian] added a comment - 05/Mar/03 12:09 AM

Sort order should be more consistent with priorities in RC4 and later.

[ Permlink | « Hide ]

Jed Wesley-Smith added a comment - 01/May/03 12:41 AM

We are seeing the same thing for our custom priorities (in this case someone totally replaced the old set), where PRI 2 comes before PRI 1 in the sort order. Our priorities are:

PAR Must be running for PARALLEL run
PRI 1 Must be running from DAY 1 of GO LIVE
PRI 2 Must be running in PRODUCTION from DAY 30 of GO LIVE
PRI 3 (default) Must be running in PRODUCTION from DAY 60 of GO LIVE
PRI 4 Must be running in PRODUCTION from DAY 90 of GO LIVE
PRI 5 Not particularly important, tad annoying

and the order they present in is:

P2, P1, PAR, P5, P3, P4

this is running JIRA Version: 2.0.2-#46 which is RC4 isn't it?

[ Permlink | « Hide ]

Edwin Wong [Atlassian] added a comment - 07/May/03 03:16 AM

Hi,

Thanks for the report.
Yes, it was a bug. We were searching by priority ids rather than sequence. This should be fixed in the next release.

Cheers