You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm facing a problem with an automation system.
I setup a set of automation rules for one of our Jira projects.
The numeric values of some custom fields within subtask should be automatically consolidated within a custom field in the parent issue.
This function perfectly when I directly modify the numeric value in the subtasks: this triggers the automation, and the parent issue is updated as intended.
But when the subtask's custom field is modified through a transition, this doesn't trigger the parent ticket update.
This is an issue, because for organizational issue, aside administrators, in this Jira project, users should only be allowed to modify the issue through a transition screen, and never directly.
As such, users make use of the transition screen to update the custom field in the subtasks, but this doesn't trigger automation, and the parent issue is never updated.
Is there a way to make sure changes to fields within a transition screen are also taken into accound to trigger the automation?
Any help would be welcomed.
Check that you include the Transition issue value for when the field value is changed. It will be under the For field.