nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to Hide/Archive 'Done' Issues from Scrum Board and Backlog?

Alex Boghossian

We have a large backlog at the moment for a project and we always pull in a large amount of issues for each active sprint; as we complete issues, the last column on our board ('Done') piles up.

What is the easiest and most efficient way to archive these 'Done' issues? In the past, I have went to the Backlog, checked each 'Done' issue in the Sprint section, then dragged all these issues to the bottom of the Backlog section. When I did that, these 'Done' issues disappeared from the Backlog section. They did not get deleted; however, I had to search for the issues to find them.

Is there an easier and more efficient way to do this? I do not want any 'Done' issue to show in our board or the backlog - but at any point, I want to be able to review which issues we have already completed throughout the project.

Accepted answers

Alex Boghossian

Lol well a simple ChatGPT prompt helped solve this issue, for anyone curious, it suggested I create the following custom filter:

project = "Your Project Name" AND statusCategory != Done

This solved my issue, when filter's applied, no "Done" issues (last column on Scrum board) show on either the board or in the backlog

All comments

Trudy P Claspill

Hello @Alex Boghossian ,

Given that you are working with a Scrum board, Done issues will display until the Sprint is completed.

You could use a Quick/Custom filter to toggle the display of the Done issues.

Varsha Joshi

Welcome to the community @Alex Boghossian ,

I always create a quick filter in my Jira projects to show only items that are not resolved or completed.

JQL -

status NOT IN (Resolved, Closed). This way I can toggle on what was completed and what issues still need to be addressed.

Hope this helps!

-Varsha

Laurie Sciutti

Hello @Alex Boghossian and welcome to the Community!

Assuming this is a Scrum board, you might want to add a Quick Filter to toggle what is visible. For instance, a QF = resolutiondate is EMPTY OR resolutiondate >= -1w would eliminate issues from your board that were resolved over a week ago.

If this is a Kanban board, you can specify time frame for how long completed issues remain on your board (via Configure Board > General tab as shown below).

HTH

Alex Boghossian

@Trudy P Claspill thank you for your answer. To clarify, issues in our 2-week Sprints tend to be left open; upon "completing sprint" I always select the option that moves however many open issues there are to the new sprint. As a result, the board does not change, including the number of Done issues on the lat column of the board.

Considering this - is the best solution to use a Quick/Custom filter to toggle the display of the Done issues? If so, what is the exact custom filter I need to create and where exactly do I go to do that?

Trudy P Claspill

If you have non-subtask issues in the right-most column that are moving to the next sprint, that is not proper functionality. It is a separate issue that should be investigated.

Subtask issues in the right-most column will move to the next sprint if their parent issue is not also in that column because all subtask move with their parent issue into and out of sprints.

Can you provide more information about the content of the right-most column not changing as you complete sprints? There should be a pop up that tells you how many completed and open issues are in the sprint. The counts will not include subtasks. Are the counts matching what you see in the board?

Alex Boghossian

Trudy P Claspill

Well, yes, that does work. Are you using that as the board filter or as a secondary custom/quick filter that you toggle on and off for the board?

If you use it as the board filter, then when you move the issues to the statuses in the Done Status Category they also will no longer show in the Sprint reports. I believe (though haven't tested yet) this will have an adverse affect on your Sprint reports like your burn down chart.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud