Automation - creating multiple subtasks throughout workflow Edited

[Christina Leong]

I have a very detailed, complicated workflow. There are 10 different status types, and 3 of them require subtasks to be created. 

In the first subtask creation, see screenshot #1, the rule works. 

In the second subtask, see screenshot #2, when I trigger the rule, the new subtask has a status of "BCT Oversight" rather than "CMO Review". Is this because I cloned the first rule? Can someone please advise? Thank you

[Bill Sheboy · Accepted solution]

Hi @Christina Leong  -- Welcome to the Atlassian Community!

For the #2 rule you note, please review and post an image of the audit log from an execution when the behavior occurs.  This may provide some context to help the community offer ideas.  Thanks!

And just to clarify rule behavior...

• In the rule you create a sub-task and then branch of sub-tasks for the parent issue
•  Branches spin off independent processing for each issue (asynchronously) and so there could be a timing issue where the just-created issue is not "caught" in time for that processing branch
• Is that what you intended?

Best regards,

Bill

[Christina Leong]

Thanks for your reply @Bill Sheboy 

I want the branched actions to apply to the newly created subtask. Should I create it as a new rule instead? Thanks

[Bill Sheboy]

Hi!  No need for another rule...

One of the available smart values is {{createdIssue}} (or {{createdIssues}} when you have several).  That value is immediately available once the issue is created, so you could branch on its key when you only need to access that one: {{createdIssue.key}}

[Christina Leong]

Problem solved! I missed an edit in the second to the last step of the rule.