nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Create a weekly Task and Subtask

Corey_vinnedge

I'm having trouble matching my questions to previously answered questions, even though there are a lot of similar questions.

I would like to create a weekly reoccurring task using automation. This is no problem. I would then like to automatically assign a few predefined subtasks to the task. This is where I'm having trouble. I tried using the branch option and just adding additional steps in automation, but its just spitting back an error. I looked at creating a whole new rule for the subtasks, but I can't see how to attach it to the specific task and not all tasks.

Thank you for your assistance. This seems like a pretty basic questions, but I'm struggling to find the answer.

Accepted answers

All comments

Keith Jones

What error are you getting when using the branch? We do something similar, but we don't have any branching. We just use Create New Issue - Issue Type = Subtask, Parent = Current Issue. I wouldn't think that the branch would impact the step for creating a new issue. Maybe try a test automation script where all you do is, on a certain status say, create a new issue.

Corey_vinnedge

I tried it with the Branch and without. I was just testing out different suggestions. The error message I'm getting is, "Issue type is a sub-task but parent issue key or id not specified. (issuetype)"

Keith Jones

Do you have Parent Issue set as "Current Issue"? in your subtask step?

Keith Jones

Bill Sheboy

Hi @Corey_vinnedge -- Welcome to the Atlassian Community!

For a question like this, please post an image of your complete rule, images of any relevant actions, and an image of the audit log details showing the rule execution. Those may provide context to explain the symptoms you are observing. Thanks!

Without seeing those...

I wonder if this is either a branching or timing problem in the rule. A typical rule to do what you ask is:

trigger: scheduled, with no JQL
action: create an issue (e.g., story or task)
branch: on most recently created issue
- action: create sub-tasks (adding as many as needed in one step)

How does this compare to your rule?

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud