When doing a list view, it appears that when I add a column to my view and sort on it, nulls always wind up at the bottom of the sort, regardless of whether I sorted Ascending or Descending.  e.g. sort comes out 1,2,3,null or 3,2,1,null.  Null is never "first" in my sorted output. 

This feels like a poor default, especially when dealing with more than 25 items.  I'd like nulls to be either sorted as "always before the first" or "always after the last," such that SOME sort order will bring nulls to the top of the list. 

Here's the bit that got me:  I was trying to find all the stories that had a null estimate.  My quick way to do this was to create a grid view, add an "Estimate" column, and sort on it.  When I sorted on estimate descending, all the nulls go to the bottom, so I see estimates of 1, then 2, then 3.... with nulls sent to the end of the list  Then I revered the sort.  Now I see 8....5....3...but again nulls go to the end of the list.  Because I have more than 25 items, and few nulls, I NEVER see the nulls on the first page. 

Unless I think hard about Mingle's default, I would logically assume "Since I sorted both ways and didn't see any nulls, that means that there aren't any nulls."  I caught it in this case (because I knew for sure there was at least one null), but a novice user might not.  Consistently sorting nulls as "before the first" or "after the last" would have solved the problem (ONE of my 2 sorts would have put the nulls first).

This is sort of related to my general complaint that grid view has a lot of quirks when there are more than 25 items that tend to reduce usability, but that's another post....

(edit for clarity)