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; } } }

Epics that span multiple fix versions

Loza

I'm introducing the issue type of epic to our team, and I have a question about how they'll affect our ability to release versions.

Our epics often span multiple releases. If I have an epic with fix version 1 and fix version 2, will I be able to release fix version 1 even though the epic will still be unresolved & not closed?

Accepted answers

Kinto Soft

to ensure that nothing assigned to that version is still pending

There are plug-ins in the Marketplace that could help you. For instance, the Links Hierarchy Structure. It allows you to explore Epics and versions from many point of views and ensure that nothing relelevant is missing:

A) The hierarchical version report collects any issue fixing and/or affecting the target version, thus you can easily see what is included/missing in the release and any dependencie too.

Or you could also explore the release from an Epic point of view from many locations: from the Epic issue page -> unmark any undesired version and left marked only the target version and maybe unversioned issues. You could combine it with the resolved filter to view only pending issues.

Regards

Pablo (the plug-in author)

All comments

Timothy

Sure. Why not? An issue can have multiple fix versions.

Loza

Thanks for your response, Timothy. I thought one of the values of releasing a version is to ensure that nothing assigned to that version is still pending. Am I missing something?

Timothy

So, which do you want? Epics with multiple version or not to break the values?

Kinto Soft

to ensure that nothing assigned to that version is still pending

A) The hierarchical version report collects any issue fixing and/or affecting the target version, thus you can easily see what is included/missing in the release and any dependencie too.

Regards

Pablo (the plug-in author)

Loza

As is typical for a product manager, I want both

Welcome!

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

Quick Links

Find more posts tagged with

jira