You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?