Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation - creating multiple subtasks throughout workflow Edited

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

1 accepted

1 vote
Answer accepted

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,


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

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

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
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

275 views 8 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you