Create Tasks and subtasks for BAU on sprint start

Dane
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 30, 2023

Hi, I'm using jira Automate to create a story - General tasks
When a sprint starts for my team

I'm hoping to expand that functionality and create a sub task per team member for meetings and admin

I.E
Story is - General Tasks
Sub task is - 'Dane - Meetings and admin'
Second sub task is - 'Tim - meetings and admin

I can create the story without issue
But how do I add the subtasks underneath it? 

If I try adding a "subtask" I get "Error the rule has been configured with components that require issues to be provided by the trigger."

If I add it as a task underneath the story that will create the task without issue but it does not add the parent link to the task it's creating 

I saw some advice online about splitting this into two separate bits of automation but I'm not entirely sure how to link the issue to the task 

Note my team is 6 people, I don't need to be able to dynamically name and assign the tasks but having that context might be useful so any approach is fine by me 

2 answers

1 accepted

0 votes
Answer accepted
Ste Wright
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 30, 2023

Hi @Dane 

Can I confirm the rule is...

  • When a Sprint starts
  • Create a Story called "General Tasks"
  • And then create several Sub-tasks

...is this correct?

I assume the Sub-tasks are static (i.e you'd create a number of separate Sub-tasks through Actions, one per user)?

---

If yes, this rule should work...

  • Trigger: Sprint Started
  • Action: Create Issue
    • Project = Project Here
    • Issue Type = Story
    • Fields...
      • Summary = General Tasks
  • Branch: Related Issues
    • Type = Most recently created issue
      • Branch-Action: Create Issue
        • Project = Project Here - must match Story's Project
        • Issue Type = Sub-task
        • Parent = Current issue
        • Fields...
          • Summary = Dane - Meetings and admin
      • Branch-Action: Create Issue
        • Project = Project Here - must match Story's Project
        • Issue Type = Sub-task
        • Parent = Current issue
        • Fields...
          • Summary = Tim - meetings and admin
      • ...etc

---

The Branch allows you to continue to create issues, whilst referring to the original Story created within the same rule.

Ste

Dane
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 30, 2023

Thanks this worked for my use case!
Appreciate the assist

Like Ste Wright likes this
0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 30, 2023

Hello @Dane 

Welcome to the Atlassian community.

Whenever asking for help with an automation rule it is helpful to use if you include screen images that show your automation rule and the details of each step of the rule. We can't advise you on why it is not working or how to fix it without that information.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events