Hello everyone. We moved from another tracking system to Jira and now we have a lot of Epics and tasks. I faced with the next problem: We need to have swimlanes by epics but completed or "marked as done" Epics don't disappear from the board and swimlanes, so now I have a bit more than 2000 tickets in the "Done" column.
Also maybe you can advise me how to pin the Done column but leave the Done status from it, for I will be able to move cards to Done column and cards get done status but would not be visible on the board?
Thanks in advance!
I was really frustrated by this and ended up making a custom filter :
!(status = Done and resolutiondate<-90d)
this ended up doing what i wanted.
agreed with Paul too - i made this a Quick Filter that i could toggle on/off which served my individual needs, so this gets my upvote.
i also recognize that i should work with my project team to create Release Versions with more regularity, which would work great with other solution proposed by @Trudy Claspill and @Bill Sheboy previously. thx for both suggestions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Mark Korolik
Based on my experiments with a kanban board using Epics as swimlanes, I found that even for resolved Epics with child issues resolved older than the "Hide completed issues older than" option, the Epics and their completed child issues remain on the board. There are two ways to deal with this.
Assuming that your "Marked As Done" Epics have their Resolution Date set, you could modify your board filter thus:
project=ABC and (resolutiondate>-14d or resolutiondate is empty)
That will clear from your board any issues that has a resolution date that is 14 days old or older and display only the issues that either are not resolved (have no resolutiondate) or have been resolved in the past 14 days. This also removes the Epic swimlanes for Epics resolved more than 14 days ago.
I did not check to see what happens if you erroneously marked an Epic as done and it still had child issues that were open.
The other options is to add a Fix Version to your issues and Epics that are completed, and set that version to Released, while also having this subfilter applied to your board.
With the above sub-filter, an issue that has a Release Fix Version assigned to it should no longer be displayed on the board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, and...to what Trudy suggests:
I recommend adjusting the Kanban board sub-filter for this need, perhaps adding the resolution date if you do not want to use versions.
If you instead change the main board's filter to solve this, those issues will be removed from any of the built-in reports that you may be using (e.g. CFD, control chart, etc.)
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good point @Bill Sheboy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Atlassian community.
Glad to know that your tracking system moved to Jira!
So here for hiding the Epic issues on Kanban board with Done or Completed status, we can then change the board filter from board setting as below :
Project =ABC and not (status in (Done, Completed) and issuetype=Epic and resolutiondate>-1d)
Hope this helps.
Regards
Shruti
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, it didn't help. Tried different options but to no avail. My tracks are based on epics, but the board shows all the epics in the project, and I only want the active ones (which are not "Marked as done" in Backlog).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.