Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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


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
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 06, 2019

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


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
AUG Leaders

Atlassian Community Events