How do I manage closed issue that are not released in next version in Kanban

I have recently started to use Kanban for managing a project using Jira.

We are about to release a new version (say 1.1), and while we are still stabilizing the release other developers continue to close issue for the releasing after that (1.2). The Done column on the Kanban board contains all issues that are Done (both 1.1 + 1.2) but I am not going to release all of it only 1.1. How do I restrict the Dome column only to show and release version 1.1?

1 answer

1 accepted

Accepted Answer
0 votes

That's not how Kanban works - you're supposed to release everything in the column and move on.

Not a problem though, because your process isn't Kanban, you just need to do things slightly differently.  Go to plain JIRA, run a filter for all the stuff you want to release in 1.1 and use bulk-edit to set the version to 1.1

I see what you mean. This is probably because we still are in a transition phase where we need to release important fixes, without included a major change that needs a lot more testing.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

21,267 views 2 7
Join discussion

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