Epic’s “Fix Version” field to automatically receive the same value as the Story’s “Fix Version” fiel

Question

I’m having some difficulties creating an automation in Jira.
The goal is for the Epic’s “Fix Version” field to automatically receive the same value as the Story’s “Fix Version” field whenever it is updated.

Could you please help me with this?
Thank you very much in advance!

Best regards,

Bill Sheboy · Answer

Hi @MARCO ANTONIO TOTH

Just following up to check if this answered your question.  If so, please consider marking this one as "answered".  That will help others with a similar need find solutions faster.  If not, please let the community know what help you need with the rule changes.

Thanks!

Jayesh Raghuvanshi_qb6277 · Answer

@MARCO ANTONIO TOTH

Set up a Jira automation that triggers when a Story’s Fix Versions changes, branches to its Epic (Parent), and sets the Epic’s Fix Versions to match the Story’s value. This keeps the Epic aligned automatically whenever the Story is updated

* Go to the project’s Automation (or Global automation if you want it reusable) and create a new rule
* Add trigger: Field value changed, and select Fix Versions (any change type is fine)
* Add condition (optional but recommended): Issue type equals Story to scope the rule to stories only
* Add Branch rule / related issues: Parent (this targets the Story’s Epic in Cloud)
* Inside the Parent branch, add action: Edit issue fields → Fix versions → use “Copy from…” → Issue to copy value from: Trigger issue → Field to copy: Fix Versions
* Publish the rule and enable it; test by changing a Story’s Fix Versions and verify the Epic updates

Reference KB articles

https://support.atlassian.com/automation/kb/automation-for-jira-different-ways-to-copy-the-value-of-a-field-into-another/

https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/

https://support.atlassian.com/cloud-automation/docs/branch-automation-rules-to-perform-actions-on-related-issues/

Thanks
Jayesh R

Bill Sheboy · Answer

Thanks for that information.  I recommend starting with learning about rules and creating a simple test rule to confirm it works as you want.  Then add additional cases and handling.

As you have not written a rule yet, I recommend pausing to learn about automation by reviewing the documentation and any of the free training content from Atlassian.  That will help you know how to proceed and how the handle any challenges.

* https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation
* https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/
* https://community.atlassian.com/learning/catalog?search=automation+rules

Next, consider how you want this update to work.  Are there multiple Fix Version values possible in the different Stories, and all of them should be in the parent Epic?  Or, are you expecting only one value?  Understanding this will help when testing your rules.

Next, consider when you want the Fix Versions field synchronized between the Epic and its child work items, such as Stories.  The simplest case is detecting a change to the field in a Story, and updating the Epic for any additional versions.  For example:

* trigger: Field Value Changes for Fix Versions
* condition: issue type is Story
* branch: to parent (the Epic)* action: edit work item, adding the Fix Versions from the trigger work item using a JSON update expression

But that will not be enough when you want all cases covered...which could require multiple rules.  These are some of the cases to consider, and so may require multiple rules with different triggers:

* when the Fix Versions change in a Story, update the parent Epic
* when a Story is created with a parent, update the Epic
* when an existing Story is added to a parent, update the Epic
* when a Story is removed from a parent, update the previous Epic parent
* when a Story moves to a new parent, update both the current and previous Epics
* when a Story is deleted, update the previous Epic
* when someone manually edits the Epic, should it re-synch with the child Stories?
* when Atlassian has an outage preventing rule execution, in is unclear which rules will run later to "catch up"; in this case, a scheduled trigger rule with JQL could be used to check / update the Epics
* etc.

Some of these cases can be combined into fewer rules.

Or, you could create a single rule with a Scheduled trigger with JQL, and only update the Epics every few hours...rather than as soon as the Stories change.