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!


Inherited Fix Version when Story is linked to Epic, and Epic is linked to Version?

I use stories  --> Epics ---> Version.

So a story that is tagged with an epic that is linked to a version should inherit the version at the story level. Shouldn't this be the norm? It appears that I have to tag each individual story with the Fix Version even though I have already set the relationship. Why does this not inherit properly?

4 answers

I don’t appreciate the knuckle-dragger comment. Inheritance should work this way as an option. It is not about savvy PO’s, it is about they many different kinds of projects people who use JIRA run. Not all are software development projects. The config should be agile enough to work for all project types. 

I was agreeing with you. I didn't like Jeff Curry's reference to savvy PO's not doing it this way as I also want to do it this way.

Knuckle dragger in question is myself


2 votes
Jeff Curry
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 16, 2018

From :

Versions are often developed over a set of sprints, much like epics. Savvy product owners may choose to deliver an epic over several versions. An epic does not have to be fully contained within a version. By delivering an epic over several versions, the product owner can learn how the market is responding to that epic and make calculated decisions about its future direction rather than doing one giant release.

Bernard and I must not be savvy - as I admit to desiring this same sort of inheritance. It'd be nice (and more flexible in a broad way) to be able to define the contents of a version using a JQL filter.

That way, if knuckleheads like me wanted to line up a version based on Epic Link(s), we could - not to mention all the other sorts of sophisticated filter types you could build to automatically keep your version contents current.

Like # people like this

same requirement

I have the same requirement.

Any solution out there?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events