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, team '25, conference, certifications, bootcamps, training experience, anaheim ca,

Want to make the most of Team ‘25?

Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.

Learn more
AUG Leaders

Upcoming Jira Events