nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

BernardH

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?

Comments

Jeff Curry

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.

unknown

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.

Steffen Rietzschel_4zak7j

I have the same requirement.

Any solution out there?

Tim Owen_xopey8

same requirement

BernardH

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.

Tim Owen_xopey8

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

advanced-roadmaps

epic

version

inherit