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

[rajanibs]

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

[Earl McCutcheon]

Hi Rajan,

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

• 8 steps to kick off quarterly planning
• Jira Portfolio: the fundamentals
• Epics, Stories, Themes, and Initiatives

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:

Regards,
Earl

[rajanibs]

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?