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 archive a ticket

Céline sapinho

Hi,
I'm trying to archive a ticket but I don't know how.
I don't want it to be deleted or to be moved on the finished tasks. I really want to keep it in an archive space. Is it possible or maybe should I create a new table nammed "Archive" ?

Thank you for your help !

Céline

Accepted answers

Brant Schroeder

Celine,

In Jira Server and Jira Cloud the only way to archive on the server is to hide the issues from individuals or exporting them and deleting them off of the instance. Jira Enterprise has built in archiving.

The easiest way to accomplish an archive of an issue would be to create a project that no one can view or access and move the issue into that project.

All comments

Brant Schroeder

Celine,

The easiest way to accomplish an archive of an issue would be to create a project that no one can view or access and move the issue into that project.

Céline sapinho

Brant,

Thank you for your answer, I'll create a new project, that's the best idea.

Have a nice day

Joao Carriço

Hello Brant,

I've seen that Archiving issues in Jira Software is only available for Data Centers.

I would like to ask regarding the solution you proposed: Will we be able to keep the history of the Issue to plot Reports? Is any information affected/lost in the process?

Thank you

Brant Schroeder

Joao,

If you are moving them to a different project you can run into information loss. You can loose custom field or field information if they are not associated with the project. so if I had a custom field on project A but did not have it associated with the archive project and I move it that information would not be available. The issues history is retained as are the links, attachments, etc. I would suggest setting up your archive project and then testing it with a test issue(s) from the project you will be archiving. We usually try to archive projects as a whole so archive them whole project when it is done. This eliminates the issues listed above. I have also see issue security used to retain issues in the project but not visible which helps with reporting and is less steps in my opinion. Just depends on what you are doing.