Jira is executing too fast and skipping automation rules

[Jess Sherman]

I have it automated so that when subtasks are complete, the parent issue is transitioned to the next column where more subtasks are assigned. The issue is that sometimes it transitions and sees that the subtasks from the previous column are complete and skips it again without assigning the new subtasks. I don't know how to add a wait time to get the subtask automation to run first... Am I overthinking this problem?

[Bill Sheboy · Accepted solution]

Hi @Jess Sherman 

The symptom you describe could be from timing issues for triggers, overlapping rules, asynchronous processing, and/or a rule usage issue.

Would you please post images of your complete rule and the audit log details showing an expected and unexpected rule execution?  Those may provide some context for the community to offer suggestions.  Thanks!

Kind regards,
Bill

[Jess Sherman]

Hi Bill,

So here's the audit log of the Parent issue. If you notice it transitioned twice and then assigned subtasks twice instead of transition -> subtasks -> transition -> subtasks. I've also attached screenshots of the two transition rules and the first subtask automation. Hopefully this helps to clarify the issue. I'm still pretty new to this tool, but hit the ground running! Appreciate the help.

[Jess Sherman]

[Bill Sheboy]

Thanks!  Would you also post images of the audit log details from the rules themselves?  That will show the details of which steps the rules followed.

[Jess Sherman]

[Bill Sheboy]

Thanks for those details, as they explain what I believe is happening:

Both rules to transition the parent are being trigged when the subtask move to done, and it is a timing issue of exactly when one updates the parent...and then the other rule updates it again to "LOI Executed".  Further still...it is possible the third rule which creates the additional subtasks may be running at the same time!

To break this link, you may need more of a redesign...What if you created the additional subtasks in the first rule before you transition the parent to "LOI In Progress" and eliminate that 3rd rule?  That will reduce the chances of both rules proceeding past the condition on the parent's status.

• trigger: issue moved to "done"
• condition: issue is a subtask
• condition: parent status is "Parcel Needed"
• branch: on parent
  • condition: all sibling subtasks are "done"
  • action...create all of the additional subtasks needed from the other rule
  • action: now transition the parent to "LOI IN Progress"  The processing before this point may add enough of a delay to break the chained execution.

Ultimately, this comes down to timing, and if the above does not work, we can try other approaches.

[Jess Sherman]

It worked! Thank you so much.

[Bill Sheboy]

Awesome!  I am glad that helped.