Kanban not hiding "Finished" tasks after 1 week

[Jason Chayer]

I am running into an issue where my Kanban board is set up to hide all "Finished" tasks after one week. However, it is showing all "Finished" items. 

I looked at when some of them were updated and several were well over 1 week ago. 

The far right hand column of my board is for "Finished" items. In looking at the board configuration, the far right column has a status of "Finished" and I verified everything in that column has a status of "Finished."

[Trudy Claspill · Accepted solution]

Hello @Jason Chayer 

Can you show us the Configure Board > General page, showing your setting for Hide Completed Issues?

Can you show us the Configure Board > Columns page, so we can see the mapping of Statuses to Columns?

Can you show us a specific issue that is being displayed in that column that you think should not be displayed? We'll want to see the Status/Resolution info for that issue, and the timestamps that appear in the lower right corner; i.e. 

[Jason Chayer]

@Trudy Claspill - I will have to wait another week before looking at this. I had to perform a bulk update; therefore the updated date will now be less than one week.

[Jason Chayer]

@Trudy Claspill - this is still an issue. In looking at the resolution field on the post function, once the item is finished the resolution field shows "Completed," which is how I set it up. However, does it need to show "Finished" since that is the status as well?

[Trudy Claspill]

Hello @Jason Chayer 

I did not realize I had not replied to this.

If this is still an issue can you show us:

1. The Status/Columns mapping for your board

2. An image from the board showing an issue that you think should be hidden. You can obscure all the data, just point out the card that you think should be hidden.

3. The Resolved and Updated date information for that card.

[Jason Chayer]

@Trudy Claspill - no problem, thanks for reaching back out.

[Trudy Claspill]

Thanks!

I've set up a test on my own board. Now I'll need to wait a week for the issue that I transitioned to age. I've set a reminder for myself to check it, so this time I won't forget. ;-)

[Jason Chayer]

Thanks @Trudy Claspill , hoping you can find something.

[Trudy Claspill]

Hello @Jason Chayer 

Well, I've got good news or bad news, depending on your perspective.

In my environment I have set the Hide Completed to 1 week and transitioned an issue 7.5 days ago, and it is still displaying on the board. However, my scenario was not identical to yours.

My issue is in the right most column, its Resolution field is set, and both the Resolved and Updated timestamps are identical and 7.5 days in the past. But its Status is an "In Progress" status.

So, I'll do another test with an issue that is in a "Done" Status to see if I get the same result.

[Jason Chayer]

@Trudy Claspill - thanks for getting back to me. 

Your comment helped me figure it out. And, as I thought, it was a simple oversight.

Even though I have everything mapped accordingly and have a resolution field set, I forgot to set my "Finished" status with the category Done.

As soon as I made that change, my board updated immediately.

Thanks again for trying to find the issue.

[Trudy Claspill]

I'm glad you found the root cause.

If my responses helped you figure out the issue please consider clicking the Accept Answer button to mark your post as Solved.

[Randy O_Neal]

@Jason Chayer I stood up 7 different company-managed Kanban boards, and we maintain a 2-week time limit on completed issues for all 7 Kanban boards.  From my experience, we've had a number of issues which seem to not go away on cue; in every case I've investigated, there's been some sort of update to the issue after its initial transition into the Done status - an update to a label, a fix version, a comment, etc. - which resets the timer.  Eventually, the timer is finally triggered and the issue rolls off the board.

What I have also found is that our sensitivity to how/when these issues roll off the Done column has also lessened significantly.  Once we had everything established and we verified things were working, our focus shifted to the actual work and not the tracking of the "paperwork".  I'll be the very last person to state that tracking Jira statuses is not important; it is, and we need accurate accounting of all our efforts.  However, we've become far more focused on the actual work we're doing; looking to the past and wondering why it's not rolling off our board has become irrelevant to us - the actual code we're delivering has become paramount.

Hopefully this issue can be resolved for you - good luck!

[Jason Chayer]

Thanks @Randy O_Neal , and I agree. My focus is not necessarily on the rolloff, as that is not important to me. 

However, I do not like seeing a long list of completed items that should have been rolled off. That is the ocd in me.

I am sure it is something simple that I am missing. I have looked at the updates, and based on that, they should be rolling off.