You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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: