How to handle story cards in Kanban
We usually work with stories and split them into subtasks as part of the planning meeting. Some smaller tasks will not be split.
We'd like to work with Kanban column limits, but find Jira's way to treat stories and subtasks confusing (Jira Cloud): A story that is split into subtasks remains a card by itself. This story card can move independend of its subtasks. Also this story card plus the subtasks are counted and compared with the limits.
See screenshot:
The WiP limit of 3 is exceeded since there are 1 task and one story plus its two subtasks in WiP.
I consider the story to be a grouping of the subtasks, so that I'd expect the number of tasks in WiP to be 3 instead of 4.
Jira Kanban boards can be configured to ignore subtasks, but cannot ignore subtasks.
Is there a way to change the behaviour?
How are other people handling stories with subtasks in Kanban - where do you expect the story card to be depending on the state of its subtasks? Are you automating this or moving the story card manually?
0 comments
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Improve user experience across Jira with global settings
Learn how to set up and configure a Jira site, manage Jira permissions, and configure Jira apps and integrations.
Learning Path
Streamline projects across Jira with shared configurations
Build Jira work items with reusable configurations called schemes, and reduce administrative work with automation.
Learning Path
Become an effective Jira software project admin
Set up software projects and configure tools and agile boards to meet your team's needs.