At the beginning of a project, we use EPIC prioritization before the EPICs are broken into stories to direct the design teams to the highest priority work in a project. Even as the project gets underway, we would like to use EPICs rather than stories further down in the backlog to prioritize work. However, the current method of changing the rank on an EPIC by drag and drop in filter panel of the scrum board is very cumbersome, once you have more than 10 or 15 EPICs.
The shortcuts for changing rank on other issues don't seem to work on the EPICs in the filter pane.
I am not so worried about ordering the stories based on the EPIC ordering, although this might be nice at the start of a project. I am happy to order the stories independently of the EPICs.
I really just want and easier way to order the EPICs in the filter pane, other than drag and drop. If we could have the shortcuts (send to top and send to bottom), plus the ability to multi-select for operations on the EPICs in the filter pane, it would be great.
However from your reply, I guess there is no way to order EPICs other than drag and drop in the filter pane or your suggestion 1 above?
There are a couple of ways you can move closer to achieving the prioritisation by Epic.
Sorry there is not a quick way of reordering the stories based upon your Epics ordering.
Not only is it annoying, but the priority is not sticky at all. As a product manager, I need the ability to prioritize Epics and stories with in each Epic and I need the priority to persist. Outside of this I still need the ability to prioritize the backlog as separate entity and have that persist in the backlog view as well as the kanban view. The Epic priorities serve as a pre planning area to help POs and BAs to really granularity set priority. The backlog could have stories from many epics being done at any given time and should be able to be managed almost as super Epic. The biggest deficiency I see in the Jira product based on other Agile tools is the lack of the Feature level, so having these priorities work appropriately is even that much more important.
Better management of epics allows to do longer term strategic planning.
Being able to score them, categorize them, and so on would make it easier for product manager. We have hundreds of large product ideas in our backlog. (which are essentially all Epics)
Until then, my product backlog needs to remain in a spreadsheet. Seems silly given how long Jira has been around.
Hi, I'm just starting with setting up our project (in JIRA Software, classic project, scrum board) and so far it sounds like the easiest way to order epics is the option 2 suggested by Phill in this thread, ie "use a Kanban board using a filter based solely on the Epics to prioritise the Epics in advance of working on the sprints."
I checked and confirm that the ranking you give to epics relatively to each other inside a column on a Kanban board gets reflected in the main issue Backlog of your JIRA project. So such Kanban boards can come in handy when you want to prioritize things of the same nature. I'm thinking of using another Kanban that filters out only the issues of our backlog that have the label "techDebt".
For advanced and more robust roadmap/release management, it sounds to me that JIRA Portfolio was designed exactly for that purpose: https://www.atlassian.com/software/jira/portfolio/features. But I haven't tried it, so can't say much about it. I'd be curious to hear experience feedback from others in the community!
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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