GreenHopper kanban and Done column

I started using GH KanBan RapidBoard and it's awesome.
However, I can see now in my "Done" column all my past issues that were done.

As this is an OPS project and KanBan board, I do not have really "sprints", "releases" or anything like that. So, how to limit the number of issues displayed in the Done column to some reasonable value? (like, this week solved issues or sth)?

3 answers

1 accepted

4 votes
Accepted answer

In general, I believe with GH Kanban, you would still 'release a version'. You can release directly from the DONE column and name a version for the issues that you have completed. You can then set the Kanban board to only show issues not in releasedversions.

At least to me, that is the workflow that fits best.

Now if you don't do releases (such as services work) then you'd need to look at a filter to do it over the whole board.

Exactly, this is a services project, but as I can see there is no direct support for no-release-projects in JIRA.

Thus, I have to stick with the filters.

I agree to Colin's solution, works for us also. However, you have to wait a couple of minutes after releasing a version, the board will then clear itself.

You could add a quick filter with something like:

resolutiondate < -5d OR resolutiondate is EMPTY

You probably meant resolutiondate > -5d. Yes, I had this solution already, but I thought that there is more generic one as KanBan is not really having releases and this is a kanban board.

I see what you mean. I'm not aware of any readily available configuration.

We had to modify the filter feeding these boards as well because it doesn't make sense to show all Done items since eternity for these types of boards. We use them for services, project implementation, and support work which doesn't have 'releases' as you indicate.

We ended up adding to the filter to show anything not in closed status and only those in closed status that have been updated in the last 30 days.

It would be helpful if the max limit that can be set on columns then only pulls based on most recent update date.

This is exactly how the boards are meant to be configured (as every team will have a different idea of what they want to see and how they want items in the last column to disappear). The work mode sub filter of the board is provided so that you can decide which issues you want to filter out there without affecting the report mode.


Great suggestion with the dates. That will work for us :)

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 29, 2019 in Jira Software

Transforming Jira Software projects for general project management purposes

...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....

204 views 0 6
Read article

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