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

This widget could not be displayed.

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 Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

139 views 2 0
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