Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,276
Community Members
 
Community Events
176
Community Groups

Jira Automation for Two Separate Tasks

Edited

Looking to complete my rule where I am able to trigger a task to be cloned when it iterated through my workflow, send an email to a user, and assign another task with a set of new subtasks to a new issue.  Any ideas on how to get the subtasks for the second issue to generate?

 

Thank you!Screenshot 2022-11-29 160407.jpgScreenshot 2022-11-29 160421.jpg

1 answer

0 votes

Hi @Michelle Garcia 

If I understand your question, you want to create the new issue (a story) and add sub-tasks to that one.

If so, after you create the new story, add a branch on most recently created issue, and put your create sub-tasks inside of that branch.  That will link them up correctly.

Kind regards,
Bill

Hello @Bill Sheboy

It seems like the subtasks didn't transfer over to the second story but the first one called.  Any other recommendations on how to proceed?

 

Thank you!

Your rule is split into a a couple of images, so I am not quite following the situation...How about this example.

  • some rule steps...
  • create a story #1
  • branch on most recently created issue
    • create subtasks A, B, C
  • create another story #2
  • branch on most recently created issue
    • create more subtasks D, E, F
  • more steps...

 

The branch on "most recently created" refers to just that, and so it needs to be placed where you want to add the subtasks.  In my example, the A, B, C subtasks get added to story 1.  The later branch associates to story # 2.

 

If this does not help, perhaps try to create a single image with your complete rule and post that image.  That may provide some context for what is not working as expected.

Suggest an answer

Log in or Sign up to answer