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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

I need to trigger an automation when modifying a field through a transition screen.



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.

1 answer

1 accepted

0 votes
Answer accepted
John Funk Community Leader Feb 02, 2022

Hi Manuel,

Check that you include the Transition issue value for when the field value is changed. It will be under the For field. 


Indeed, the problem was right there, and your suggestion helped me to fix it.
Thank you very much.


Best regards,

Like John Funk likes this
John Funk Community Leader Feb 03, 2022

Great! Glad that fixed it for you. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events