Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,366,678
Community Members
 
Community Events
168
Community Groups

Jira Portfolio - Cases where EPICs are not planned in a release

Edited

What if the EPICs are not planned in releases, but only the features and stories. There are multiple teams and dependencies, and the release is planned using the fixversion in JIRA. If we bring JIRA Portfolio, how will this help to do the planning considering that the Portfolio for JIRA does the planning at EPIC level, but we want to do this at feature and stories level

1 answer

0 votes

Hi Rajan,

Check out the Blog posts below for some more details on this:

But Epics can span multiple releases without issue, in portfolio if you choose a release at the epic level of the hierarchy it will cascade down and set all child issues of the epic to the same release, but if you do the release planning at the story level the multiple releases will cary Up and reflect on the epic like this:

Screen Shot 2019-03-06 at 6.09.53 PM.png

Regards,
Earl

Thanks Earl for the response. Currently our issue hierarchy is that Epic->Features->Stories->Sub-task. I saw in JIRA Portfolio, it is Initiatives->Epic->Stories. So, if we bring JIRA Portfolio, how can we manage the existing hierarchy?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events