Feature #6034
open
sorting should disregard blank fields
Added by Josh Sharpe over 15 years ago.
Updated about 9 years ago.
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.
Do you have update about this issue ?
It's a very disturbing issue, because for example, if you sort by Due Date or Start Date, empty issue appear first, and after that, late (and urgent) tasks.
Issue with empty date must appear at the end (far in the futur), and not far in past.
If they don't have any date, that's propably because they are not urgent at all ...
- Has duplicate Feature #3467: Due date sort order should sort issues with no due date to the end of the list added
- Has duplicate Feature #24529: change sort order for due date column on "Issues assigned" page added
- Category changed from Issues to Issues list
- Related to Patch #25066: Sort order with null placement (NULLS FIRST, NULLS LAST) added
Also available in: Atom
PDF