how to handle Closed issues for Control Chart on a Kanban board?

james_warr

We use Kanban boards and are making an effort to drive improvements by using the Control Chart report.

Once we close an issue, we would prefer to have it not show on the board, so we don't map this status to any of the columns.

However, when we do this the issue does not get included in the Control Chart at all. If we move the Closed status into our 'Done' column then the issues are included but we now have lots of closed issues that we don't care about day to day polluting our board. 

Scrum boards seem to handle this by only showing issues in the current sprint - what's the solution for Kanban? We currently apply a quick filter to hide the Closed issues, but this feels clunky to me

Walter Buggenhout

Hi @james_warr,

As the control chart is based on the board columns, you indeed need the column on your board.

You have 2 ways to keep your Done column clean: one is to periodically 'release' the issues in the right column of you board. There should be a link called 'Release ...' in the top right corner of your board. Clicking it, will assign all issues to a fix version and remove them from the board.

Another option would be to adapt the filter of your board to automatically exclude issues that were closed some time ago. e.g:

Project = ProjectA AND (resolution = Unresolved OR Resolved >= -30d)

This would automatically remove all issues that had a resolution set more than 30 days ago.

The downside of the second option would be that those issues are no longer associated with your board. In most recent Jira version, Atlassian is automatically doing similar (hiding issues closed more than a couple of weeks ago), mainly for performance reasons.