Should issues always have a fix version?

[Thomas Saxtoft]

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?

[Nic Brough -Adaptavist- · Accepted solution]

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)"