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
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:
To see this feature in action check out our recent dependencies demo here: https /www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....
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