Actions
Feature #6034
opensorting should disregard blank fields
Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues list
Target version:
-
Start date:
2010-08-04
Due date:
% Done:
0%
Estimated time:
Resolution:
Description
When sorting something in ascending order all the issues that have a blank value for this field are first in the list.
Instead, anything that does not have a value should be pushed to the end of the list. They are essentially undefined.
If I'm sorting a list of 300 isses by version number, I'm not asking to see the blank ones first -- I'm asking to see the lowest version number first.
Related issues
Actions