I had an pre-existing set of priorities:
1-RED
2-ORANGE
3-YELLOW
4-GREEN
5-PURP
6-(notset)
I added a different set of priorites (for a different project):
1-Must Have
2-Needs
3-Wants
Priority was not a required entry for my new project.
I added a set of tasks to my new project, some of which had a blank priority.
When I sorted on Priority, my blank ones came to the top (duh). I didn't like this, so I used Multi-edit and set them all to the pre-existing priority '6-(notset)' thinking that would surely put them at the bottom - but it didn't. (See attached screen shot). I would think that the sort would be on the alpha represetation of what is displayed in the column. Instead it seems to be on an underlying code value.
So I added a new priority:
9-(not established), changed all the '6-(notset)' to '9-(not established)' -- and that would sort fine.
So either
a) I'm right that you are sorting on an underlying code
- It's a 'feature'
- It's a bug
Or
b)I'm wrong about why its doing that, but its still undesirable.
Or,
c)I don't understand what is going on.