would like automation on the most recent sub-task created

Mike Espitia July 26, 2024

Hello team,

I am trying to run an automation that will check the most recent sub-task and match the story status to it. Currently the automation i have is running on every sub-task the story has and this it running up my automation usage % per month.

2 answers

0 votes
Mike Espitia July 27, 2024

Here is a screen shot of the automation. However this automotion is looking at every sub-task per story. SO I have multiple agents working on each sub-task once there change the flow it will run the automation. 

 

Jira.jpg

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 26, 2024

Hi @Mike Espitia 

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

Triggered rules only count for "usage" when they perform certain actions, and so if you add conditions to your rule that will help manage usage.  To learn what counts toward "usage", please review this documentation: https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

Regarding performing the updates only with the most recently created subtask, you could use Lookup Issues with JQL to find the subtasks and ORDER BY Created DESC.  Then grab the first one for comparison before the rule proceeds.

Kind regards,
Bill

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 28, 2024

Please try to stick to one thread when responding.  That will help others in the future see if there are multiple solution approaches to solve the problem.

 

From what you describe, perhaps someone has enabled this option at the top of the rule: "Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule."

If so, disable that so only the initial transition from the trigger issue will make updates...and so not re-trigger the rule recursively.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events