Should issues always have a fix version?

We have been using JIRA for many years and have always closed issues that were not fixed without a fix version. For example issues that cannot be reproduced are not actually fix in any version, thus we did not assign a fix version.

Not I have decided to use Kanban and I have created a Kanban board. Now in the done column there figures more than 1000 issues that do not have a fix version. Issues that was closed a long time ago, but was either Cannot reproduce, Duplicate or Limitation.

So when using Kanban what should the fix version be in those cases? Or is it possible to limit what goes in the Done column?

1 answer

1 accepted

0 vote

Kanban pretty much relies on you setting the fix version, but there's no need to set it for historical issues.  I'd just change the board filter, adding a clause to exclude "and not (status = closed and fixversion is empty)"

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,308 views 14 20
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot