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

[MARCO ANTONIO TOTH]

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]

Hi @MARCO ANTONIO TOTH -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help.  Please post the following:

• what version of Jira are you using: Cloud, Server, or Data Center
• for Cloud, what type of project is this: company-managed, team-managed, JPD, etc.
• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected and why you believe that to be the case

Until we see those...

Additionally, please consider how you want the Epic updated when the child Stories could have multiple different Fix Versions: add all the versions, or something else.

Kind regards,
Bill

[MARCO ANTONIO TOTH]

Thank you for your attention and response.

The automation hasn’t been created yet. I don’t know how to create this automation, and I kindly ask for help, as I’m not sure how to do it.

what version of Jira are you using: Cloud, Server, or Data Center
I'm using ira Cloud.

for Cloud, what type of project is this: company-managed, team-managed, JPD, etc.
It's a company-managed project

Kind regards,
Marco Toth

[Bill Sheboy]

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:

1. when the Fix Versions change in a Story, update the parent Epic
2. when a Story is created with a parent, update the Epic
3. when an existing Story is added to a parent, update the Epic
4. when a Story is removed from a parent, update the previous Epic parent
5. when a Story moves to a new parent, update both the current and previous Epics
6. when a Story is deleted, update the previous Epic
7. when someone manually edits the Epic, should it re-synch with the child Stories?
8. 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
9. 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.