Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Change custom field values based on Epic change

NSEU DevOps February 20, 2025

Hello,

I am trying to work out the best way to meet the following requirement using Jira Automation:

The custom fields "planned closing version" or "fix version/s" of an Issue within Epic" should change automatically and accordingly if its Epic "planned closing version" or "fix version" is getting changed.

However, it should be possible to change the "planned closing version" and "fix version" of an "Issue in Epic" individually without any effect on the other "Issue in Epics" or the dedicated Epic itself. 

To simplify

1. If the custom fields "Planned closing version" or "fix version/s" are changed  in an epic the subsequent child tickets can change automatically.

2. Changing the "planned closing version" and "Fix version/s" custom fields in the epic can also do the opposite and not affect the issues within the epic itself.

Am I right in my understanding by focusing on rule 2 first, as this is the one that can be automated. Whereas, rule 1 would be done by a manual trigger?

 

Thanks

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
9.12.14
TAGS
atlassian, atlassian community, university, on demand, transition to jira cloud

Transition to Jira Cloud

Switch to Jira Cloud with Atlassian University! Explore new navigation, issue views, and Cloud features like team-managed projects and automation. Tailored for Data Center users & admins, these courses ensure a smooth transition. Start your journey today!

Enroll now
AUG Leaders

Upcoming Jira Events