To keep the Kanban board nice and tight (fewer issues) we sometimes do not map the Closed State. This is easier than monthly releases or such.
Specially when running a Kanban for a pulse meeting the strategy is very effective. The team may resolve issues at any time and then at the meeting when the decision has been communicated.
You can't, directly. The point of the diagram is that it represents your process via the board, and the board should represent your process as built into the workflow. You've set it up not to.
A solution would be to have a second board set up to match the workflow and use the CFD on that (and educate the users that the first board is probably the one they want to use)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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!
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