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

What is the best way to archive issues ?

Kurt Callebaut_njs1wb

Hi,

We like to keep track of old issues. what is the best way to archive "done" issues in a project ?

Moving to another project is no option because the Issues ID is changed and renumbered, while we want to keep track of id, commits, reviews, etc..

We also want them do disappear from kanbanboard which contains "Done".

Thx,

Kurt

Accepted answers

Jack Brickey

what are your requirements for archiving. IMO, you don't need to do anything with them. What you want to do to meet your "disappear from Kanban..." is to simply add/change your kanban's sub-filter to age them off the board. Something like this...

resolved >= -4w OR resolved IS EMPTY

change the interval to meet your needs.

All comments

Jack Brickey

resolved >= -4w OR resolved IS EMPTY

change the interval to meet your needs.

Kurt Callebaut_njs1wb

Hi, thx.

That seems an option indeed. Though our teamlead archives them as manual action after reporting them to the management. So telling this now i realize we probably need and extra status "archieved".

i will suggest both option.. thanks again for the response.

Jack Brickey

FWIW, the only reason to have an Archived status is if you want to be able to separate "Done" from "Archived". IMO adding the extra step is going to come back to bite you and add unnecessary complexity. Of course that is just MO and I don't know your requirements. :-)

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