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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

1 vote
Jeff Curry Atlassian Team Feb 16, 2018

From https://www.atlassian.com/agile/project-management/epics-stories-themes :

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

I have the same requirement.

Any solution out there?

same requirement

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

 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Advanced Roadmaps

Introducing Advanced Roadmap’s new dependency report

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....

150 views 2 6
Read article

Community Events

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

Events near you