Sub-tasks for specification in Jira

We use subtask for splitting the development, so when created they have status as "ready for development" in our scrum board. But we use another named named "Master Board" where UX split their Use Stories into Sub-task related to specifications.  

Since we have by default subtask as "ready for development" when created, how can UX create sub-tasks that have actually status as "ready for specifications" or "Specification in progress" status? 

Long story short: 

Subtask created from developer="ready for development" (Developer board). Works ok in current settings

I want: Subtask created under specification = have status as "ready for specification", not "ready for development"

How to split?

1 answer

0 votes
Thomas Schlegel Community Champion Oct 10, 2017

Hi Roberto,

you can create another subtask type. Then assign different workflows to your subtask types.

But there's no automation for the type. Whenever a subtask is created, you have to decide, whether it's type a or type b.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,880 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot