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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,556,244
Community Members
 
Community Events
184
Community Groups

Jira automation does not detect issue state transition which is performed by another automation.

Jeffrey Chang
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 23, 2023

I have a task A which preceeds a custom issue B when then preceeds another custom issue C.
Task A --(preceed)--> custome issue B --(preceed)--> custom issue C


And I have two automations.

Automation 1: 

1.1. when a task changes to Done

1.2. check the custom issue which is preceeded by the task

1.3. if all tasks which preceed the custome issue (found in 1.2) are all Done, move the custom issue to Done

Automation 2:
2.1. when a custom issue changes to Done

2.2. check the custom issue which is preceeded by the task

2.3. if all tasks or custom issues which preceeds the custom issue (found in 2.2.) are all Done, move the custom issue to Done

 

Problem:

I change task A to done, automation 1 kicks in and changes custom issue B to Done automatically, however custom issue C is not changed to Done automatically. The automation 2 does not detect the custom issue state transition performed by automation 1.

However if I manually change custom issue B to Done, automation 2 kicks in and changes custom issue C to Done automatically. This proves that automation 2 set up is correct.

1 answer

1 accepted

1 vote
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 23, 2023

Hi Jeffrey - Welcome to the Atlassian Community!

For automation 2, have you checked the box in the rule Details for Allow rule trigger? If it is not checked, then automation 2 will not fire based on automation 1 firing and doing something. 

Jeffrey Chang
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 26, 2023

Thanks for the answer. After checking the allow rule trigger, it works fine now.

Like John Funk likes this
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 26, 2023

Great! Glad you got it working. 

Suggest an answer

Log in or Sign up to answer