Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Setting up automation for copying fixversion of epic to all dependent stories and defects

Please provide some automation examples in Jira for

1.  Updating all child issues (aka stories, defects) for an epic with the fixversion of that epic.

2. If the issue is moved to another epic, it then inherits the fixversion for that new epic.

3.  If the fixversion of that epic changes, all dependent issues will also change.



1 answer

0 votes

Hello @amy schneider 

Welcome to the community.

Have you spent any time reviewing the automation documentation and trying to create these rules yourself?

Are you working with a Company Managed project or a Team Managed project?

For #1 one scenario is that the child issue is being added to the epic when the child issue is created. In that case the rule would be the following (substitute Fix Versions for Assignee):

Screen Shot 2022-09-09 at 10.17.08 AM.png

For #2 this rule works (substitute Fix Versions for Assignee), but only for a Company Managed project.

Screen Shot 2022-09-09 at 10.19.14 AM.png

For #3 you would use this rule:

Screen Shot 2022-09-09 at 10.13.37 AM.png


The above does not cover the scenario where you already have child issues in Epics, and the Epics already have Fix Version values, and you now want to update all the child issues.

Suggest an answer

Log in or Sign up to answer