Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation - creating multiple subtasks throughout workflow

Christina Leong May 19, 2021

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

 

Screen Shot 2021-05-19 at 5.28.36 PM.pngScreen Shot 2021-05-19 at 5.28.40 PM.png

2 answers

2 accepted

1 vote
Answer accepted
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.
May 19, 2021

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 May 19, 2021

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
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.
May 20, 2021

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}}

Like Christina Leong likes this
0 votes
Answer accepted
Christina Leong May 19, 2021

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

Suggest an answer

Log in or Sign up to answer