There should be a feature to sort the backlog and sprint issues based on priority. this will help to organise the backlog and sprint better
Why?
It would only be of use once, when you first start trying to use ranking. Once you start to re-rank issues, the sort process would become useless because it would destroy all your rankings when used.
Remember that priority is a flat set of selections, it is not the order in which things should be done like ranking is. There are two important things about that statement - first, when you have more issues than you have possible priorities, the sort by priority can no longer have any use in choosing what to do first, and second, priority is ignorant and self-centered. What use is it to have an "urgent" issue at the top of the list when it can't be fixed until you've done something about the "trivial" one near the bottom?
There is a use for sort by priority, but it is limited very much to "when I first get a pile of issues and have no idea where to start". As soon as you move past that, it's of no use.
Umm. I slightly hesitate to agree on this point - "Once you start to re-rank issues, the sort process would become useless".
The intention to have the sort feature is to group all high, medium, low, etc. priorities together.
The ranking process in the backlog is not stagnant, it's always rolling; so as a user, if I would like to see all Medium let's say priorities together, I can achieve that using the sort feature.
Something similar to what we have on desktop "Sort by"
Right now, I have to manually drag-drop and place one after the other to group all similar issues (priority-wise) together
Ok, so imagine a really simple case - you have 5 issues and 3 priority levels. When you start your new project with those 5 issues, you do a sort by priority and end up with 2 high first, one medium, and two at a low priority.
Now, your people rank one of the low priority issues as #1 (probably because they can't deal with one of the higher priority issues until that one is fixed)
Now click "sort" again. Your two high priority issues jump up above the low priority one.
You have now broken your list of stuff to do, losing all the ranking that your people need to help deal with dependencies.
(Note, if you mean "sort only in view, do not adjust rank", that's fine, but it's pretty useless as a list sorted that way tells you nothing about the order in which you need to tackle things, and you can't rank things in such a view)
It looks like you're new here. Sign in or register to get started.
