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 Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,124 views 4 9
Read article

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