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?
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.
B) 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.
Pablo (the plug-in author)
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG