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 Subtask after all Subtasks are done

thrilos07

So right now I created this Automation Task:

Where four subtasks get automatically created once an Issues-Type of "Bug" gets created. What I want to do now is to create another two subtasks once all four of the Sub-Tasks are set to "Done". I came up with this:

But this does not seem to work. Any ideas?

Accepted answers

Sam Harding

Hi,

I posted a possible solution to the problem in your other post https://community.atlassian.com/t5/Jira-questions/Only-transition-a-sub-task-when-an-other-sub-task-is-done/qaq-p/1629325, which hopefully helps to diagnose why your current rule set up is not working as expected.

Cheers

Sam

All comments

Jimi Wikman_ex43zi

It seems like a lot of work for a bug...

May I ask why you want to create subtasks in this way, so I understand the why before I suggest a solution to solve it technically

thrilos07

Hi,

the Bug-Issuetype which got chosen here was just an example.

We do not want the Sprintboard to be full of Subtasks. We want to be done with Subtasks which are bound to "Step 1" before the rest of the Subtasks who are bound to "Step 2" show up. We just don't want to have like 6 subtasks inside of this Issue from the start.

Jimi Wikman_ex43zi

There are many solutions to solve that particular issue, but let's start with the workflow you have, so I understand what you are trying to do.

When someone creates a bug, what is that? A defect or Incident?

Secondly, what subtasks do you create first, and why do you need them? Is it because the workflow does not allow you to work with the bug in a workflow, so you create it in sub-tasks instead, or is it to force a definition of done?

As you say the second trigger should be for step 2, what is that step? Does that step have a workflow transition as well that we can use? What are the additional 2 subtasks you want to add?

thrilos07

The reason why we use sub-tasks is to break that Issue down to smaller tasks. Now, lets say we have in total 5 sub tasks, which are always the same and also are done in this order:

1. Read Bug-Report (Step1)
2. Rewrite that Report (Step1)
3. Fix (Step2)
4. Test (Step2)
5. Release (Step2)

So whenever we create a new Bug-Issue we just want the Step1 sub-tasks to be displayed. Once they are set to "DONE" we want the Step2 sub-tasks to appear in the same issue. The transition columns are "OPEN", "IN PROGRESS" and "DONE". I do not really want to change anything there, what I want is to decide when which subtask is displayed.

Sam Harding

Cheers

Sam

Welcome!

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

Quick Links

Find more posts tagged with

issue

cloud

jira-software

jira-software-cloud

automation

sub-task