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; } } }

Creating a different workflow for sub-tasks within an existing project

Michael Crincoli

Any advice on creating a different workflow for sub-tasks, within an existing project. I do not want this to be a global change across all projects, just a single project (which is set-up as a classic project).

Can this be done under Project Settings>Issue Types within the project? I can select the Issue Type (Sub tasks) and you can see the workflow that is currently persistent across all issues in project. Is there a way to edit from this area?

TIA for assistance.

Accepted answers

Adam Rypel _MoroSystems_

Hello @Michael Crincoli ,

for sure, first you need to add sub-task issue type to your issue type scheme on your project - I suppose that is done.

Then you need to create new workflow scheme for this specific project and assign the workflow to sub-task issue type. Since this workflow scheme will be used only for this one project, it won't change for the others.

This guide should help you: https://confluence.atlassian.com/adminjiraserver072/configuring-workflow-schemes-828787949.html

Let me know in case of any problems.

Adam

All comments

Adam Rypel _MoroSystems_

Hello @Michael Crincoli ,

for sure, first you need to add sub-task issue type to your issue type scheme on your project - I suppose that is done.

This guide should help you: https://confluence.atlassian.com/adminjiraserver072/configuring-workflow-schemes-828787949.html

Let me know in case of any problems.

Adam

Michael Crincoli

Thank you @Adam Rypel _MoroSystems_

All good, no issues.

Michael Crincoli

@Adam Rypel _MoroSystems_ Hi Adam - Now that the sub-tasks have a different workflow than the stories, I have an "accepted" stage for stories, which is the final stage. The sub-tasks have a simplified workflow with "done" being the final stage. I am unable to complete a sprint since the subtask are still in the done state. do you have a recommendation on how to remove the validator or automate a transition of all subtasks once the related story is "accepted"? Thanks for your assistance!

Adam Rypel _MoroSystems_

Hello @Michael Crincoli ,

if I understood correctly, you would like to complete sprint even without subtasks being in status Done.

Well all the tasks in the sprint have to be done in order to complete the sprint, so I am afraid you cannot remove that condition. You could map the Open status of subtask to Done column on sprint board (through "..." -> Board Settings). But I do not recommend that, since it does not really make "logical" sense to have Open status mapped to Done column.

As you say, you can use Automation to transition the subtasks to Done status. You can find Automation in the Project Settings. So you might create a rule similar to this:

_automation rule.JPG

Subtask needs to be in status, which can transition to Done status, otherwise the rule will fail. If you have "Allow all statuses to transition to this one" on Done status, then it should not be a problem.

To be absolutely honest, I do not recommend that either though - the users should learn to close their subtasks after they complete them, and without the automation, they just have to do that Of course your intention might be different and it is your decision.

Let me know if you need anything else.

Adam

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud