When viewing an Epic (https://jira.foo.com/browse/FOO-22) there is a list of linked issues "Issues in Epic". The list is ordered by Global Rank in descending order. I would like the list in ascending order, as nature intended. How can I configure this?
3 things worth mentioning (besides the obvious "Im wanting this functionality too")
1. either in this thread or a similar one, there is a link to the Atlassian Jira and the request for this on Jira Server (as opposed to cloud) was closed and they said not enough interest (I didn't bother reading the one for cloud, but It was still open)
2. As someone already pointed out, the "sort the backlog = sort the issues in epic" only works for things that are actually in backlog (i.e. not in an active or future sprint) which is pretty silly considering I can reorder issues in a current sprint in the backlog tab\screen
3. one thing I haven't seen mentioned that "could" be helpful for some....when you open an epic, in the "issues in Epic" section you can hover your mouse over to the far right side of each issue, and you should see a little gear icon. in that icon's drop-down I see the options "Rank to top" and "Rank to bottom" So while I doubt this helps most of us, for those who really only need to do this once in a blue moon, or don't have tons of stories, maybe this is a feasible workaround.
I’m very excited to see that this issue is coming up to five years old!
After half a decade of comments from a great bunch of people, Wilson and I have come to think of you all as our special friends.
On 27th I’ll be at the pub, in Dublin Ireland, ready to buy anyone a drink if they can figure out how to get this issue resolved.
Ex- Jira user
Guys, this way was working for me:
Just enjoy the user-friendliness of it.
Well, closed issues sure as hell aren't moved to the bottom! This drives me nuts with the stories in my Jira epics.
And the rank-to-bottom thing doesn't work for me. Not sure why.
Yet another example of Atlassian's attitude of "Yeah, we're just not going to do anything about that, even with so many people frustrated by it."
Your software is user-facing. You should be working actively to address their concerns.
/ rant off
I added numeric labels to all of the issues under a particular epic and then displayed that column too to help get them in the right order when Ranking to Top. Not the most user friendly way of setting rank but at this point I'll use what I can. :sad: Too bad this isn't a higher priority since it is such an old request and many people seem to want/need the same function.
I have this issue several times so at the end here is what I do:
I think creating a Kanban board works best for this. Make sure to clear the board sub-filter and set Hide completed issues older than to Never mind, show all though.
You might also want to exclude Sub-Tasks and the Epic itself from the board filter. E.g.,
project IN (ACM) AND parentEpic IN (ACM-100) AND key NOT IN (ACM-100) AND type NOT IN (Sub-task) ORDER BY Rank
Users no longer have the ability to edit Rank fields on the JIRA 'View Issue' page. The only way that 'Rank' fields can be changed is by drag-and-drop ranking on one of GreenHopper's boards.
If you would like to rearrange the order of the issue on your epic, you can create a board for the Epic and manually resort the issues.
create a filter to show your epics such as "Epic Link" = Issue-1234
Add a heading row above the list and provide sort capability through clicking the heading. Lots of OpenSource JS tools to do this. It'll allow for anyone's use case as long as the column is exposed.
I don't care about that ranking stuff, just want to sort by issue id.
I "fixed" my epic by listing the issues in order (I used an editor, but could easily have used a filter in another window) and then worked from last to first marking each as Rank To Top. It doesn't re-order unless you refresh, you can if you want to check progress. Tedious, but only the work of a couple of minutes.
Some of these issues have been through sprints though. I didn't spot any weird side effects from changing their ranking. I'd have hoped for a warning if what I was doing was bad...
It actually works the other way around. Ranking within the issue doesn't affect the sprint. But moving the issue in the Backlog Board to, say, the next sprint will change the order the issue appears within the epic ticket, if another issue from that epic was already assigned to that sprint!
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events