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; } } }

Archived cards

Ashley McGee

When issues are complete within my project, we put them in either the right-most column. The board is filling up and and we need to archive the issues that are considered complete. We want them off of the board, but still want to access them in the future if we need to reference what action was taken/who worked the issue. How can we do this?

Is the Release button an option?

Please note, we have not used the Resolution field, rather consider something complete when it is moved to the right-most column.

Accepted answers

All comments

Matt Robertson

Hi Ashley,

There's a couple of different ways of archiving issues from your board, depending on which kind of board you're using. Can you tell me if you have a kanban, scrum or agility board ?

Andrew Durden

Hey Matthew,

I am having a similar issue specifically with an Agility Board. Can't see to figure out how to archive tickets so they are no longer displaying in the right most column on the board when not needed.

Also had some issues with enabling the Backlog and Sprint features mentioned on this documentation: https://confluence.atlassian.com/jirasoftwarecloud/enable-agile-functionality-945104930.html

Please let me know if you could help me out. Thanks!

Ashley McGee

Hi Matt,

Our project uses kanban boards. We were thinking about using the release button to remove the tickets from the far right column on the board. Using the release buttons removes all the tickets from the column but they're still accessible/searchable, correct?

When you look at the page with the previous versions released, what is the archive button for?

Thank you!

Ashley

Nic Brough -Adaptavist-

Release simply stamps the issues with a version, so that the board "sub-filter" drops them from the board. It won't affect anything else, the issues don't change in other ways.

Brad Kelley

As a long-time Trello user, I find it difficult to accept this glaring lack of seemingly basic kanban functionality. Apparently Done items are just supposed to continue to grow forever, taking up space in the Done column and force the page to grow to an indefinite length? Our organization is moving to adopt Jira and this is becoming an unnecessary roadblock. Forum post after forum post with the same issue and no resolution. I'm flummoxed.

Nic Brough -Adaptavist-

What lack of functionality? The boards and filters all allow you to have "closed" issues disappear, while retaining the ability to find them if you need them, so I'm not sure what you are missing?

Brad Kelley

As discussed in this OP, and several others, Jira's kanban lacks the ability to merely archive completed tasks without user gyration or hackery. There needs to be a simple archive mechanism that doesn't require the creation of releases and filters. It's absurd. We've been struggling with this for weeks here, and I had not turned my attention to solving the problem until today, so forgive my frustration. I am deeply disappointed.

Brad Kelley

Perhaps I am just not understanding, and approaching this wrong. What should the workflow be?

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software