How should subtasks be used on a kanban board? Edited

We're using a kanban board but we're unsure how to represent stories that we break down into subtasks. Do we create subtasks under the parent story and move those subtask issue types through our workflow or do we create task issue types that we move through our workflow and just close the story?

It's unclear how these two methods impact things like cycle time and the documentation doesn't give any guidance. Does Atlassian recommend a particular way? What does your team do?

Thanks!

 

0 answers

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,861 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