Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.2
-
Component/s: None
-
Labels:None
-
Environment:IF 3.1
Description
This is due to an effect of EL, however this wouldn't be an issue, if the value returned instead of null, 0 didn't behave like it was a valid priority. Sort priorities should be indexed at 1, so ignoring 0 should fix this issue.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Revision #30376
Committed by nils.lundquist
A minute ago
ICE-8435- Altered sortPriority checks to accept 0 as a null value.