Project

General

Profile

Actions
Copy link

Defect #11204

closed

Priority order inconsistency

Added by Jean-Claude Wippler over 12 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid
Affected version:
2.0.3

Description

When listing issues by priority, it seems to me that these two should be each other's inverse:

Environment:

Redmine version                          2.0.3.stable.9874
  Ruby version                             1.8.7 (i486-linux)
  Rails version                            3.2.6
  Environment                              production
  Database adapter                         MySQL

Redmine plugins:

no plugin installed

Files

Download all files
prio-ascending.png (6.3 KB) prio-ascending.png Jean-Claude Wippler, 2012-06-20 11:21
prio-descending-oops.png (6.33 KB) prio-descending-oops.png Jean-Claude Wippler, 2012-06-20 11:21
Actions
Copy link
 #1

Updated by Jean-Claude Wippler over 12 years ago

Forgot file extensions - should be:

Actions
Copy link
 #2

Updated by Jean-Claude Wippler over 12 years ago

Workaround is to reverse the order on the admin Enumerations config page. I can't think of any drawback to doing it this way.

Actions
Copy link
 #3

Updated by Jean-Claude Wippler over 12 years ago

Ehm, no - then all low prio issues get shown in red. Reverted. Sorry for the noise.

Actions
Copy link
 #4

Updated by Etienne Massip over 12 years ago

  • Description updated (diff)
Actions
Copy link
 #5

Updated by Jean-Philippe Lang over 12 years ago

Just to make sure, what this ticket is about is the normal/high/low order in the screenshot on the right (should be high/normal/low instead) ? Please post the result of select name, position from enumerations where type = 'IssuePriority'.

Actions
Copy link
 #6

Updated by Jean-Claude Wippler over 12 years ago

  • Status changed from New to Resolved

Please post the result of ...

I'm afraid I don't know how to do this.

But if the left says A,B,C, shouldn't the right say C,B,A - regardless of enumeration order settings?

PS. If this was a bad ordering, I may have "fixed" it by rearranging the enumeration to try things out - I don't think the problem can be reproduced here anymore. I'll tag the issue as resolved for now. No idea how the bad state came about, but it seems to be gone now.

PPS. So the workaround - if anyone else ever gets this behavior - is to manually rearrange the enumeration and then set it back to what it was.

Actions
Copy link
 #7

Updated by Etienne Massip over 12 years ago

  • Status changed from Resolved to Closed
  • Resolution set to Invalid
Actions
Copy link

Also available in: Atom PDF