I would like to request a new Feature on the Kanban boards - to be able to add Definition of Done / policies for each column on the Kanban board - as per the Kanban core practice.
You can officially submit one in the JIRA public issue tracker via support.atlassian.com.
Curious though, what do you want to accomplish with this DoD Policies for each column? You know that these columns are configured to show certain issue statuses you set them to be and each status can have "Conditions" before it is moved to that status.
I'm curious as to what this would look like - as Gabrielle says, you're already controlling "done" by configuring the board, so all I can imagine is a textual description of the rules, which would just take up space
Thanks Gabrielle.
This is one of the 6 core practices of Kanban - making process policies explicit - and having exit policies / DoD per column is a key part of that, that many of the other Kanban vendors already have setup - eg. https://www.rallydev.com/blog/sites/rallydev.com.blog/files/productblog/2012/07/Kanban_Policies.jpeg
This allows the team to set policies and make it explicit / visual. The conditions are not JIRA conditions, but team DoD agreements, which evolve on a daily basis with some Kanban teams.
So Nic is right, a textual description of the rules that is displayed in the column headers. Try submitting this to Atlassian and see what they think about it
Azure DevOps has this feature.
It is Microsoft's competitor to Jira.
Yes, and it's robustly ignored. Like most MS offerings, it's not really a lot of use in real life.
If you're going to do Kanban, great, it's fantastic, but do it right. One thing is a common and invariable definition of done. So you don't need it on every board.
All of our teams use it. They start with a default set and improve them as their teams mature. My Jira teams are more likely to leave a column before they should because it is too inconvenient to go to the Confluence page with the default exit criteria per column.
I find it frustrating when we ask for a feature, explain how a competitor has it, only to be told it is unused or dumb that they have it. Kanban and Scrum teams make policies explicit. It is part of the Kanban way. Please stop telling us it isn't important. We post these needs because they are real and in this case, textbook.
Only workaround I came up with, works ok: http://prntscr.com/sdtt5w
It looks like you're new here. Sign in or register to get started.
