Archive a project or issue

[Lily Tsoiasue]

I believe I am an administrator for our Jira. When I try to move a project, it only allows "Move to Trash" or "Project Settings" -  archiving a project does not appear as an option for me. I do not wish for some of our projects to delete after 60 days and I see the Archive section on the left hand side of my Jira but do not see an option to move the projects into Archive.

[John Funk · Accepted solution]

Hi Lily - The Archive a project function is only available for Jira Premium subscriptions. If you want to keep it but not be able to use it (archive it more or less), then create a permission scheme that has no permission for Create Issue in the scheme and attach it to the project. 

[Lily Tsoiasue]

Thank you!

[Mara Finkelstein]

I have the same issue but am already on premium.... Any advice?

[John Funk]

Hi Mara - if you are on Premium, you should be able to go to the list of projects, then search for the project you would like to archive.

Finally, click the 3 dots on the right side and select Archive. 

[Mara Finkelstein]

I do not have an issues for archiving projects only issues.

[John Funk]

You don't really archive issues. What is it that you are actually trying to accomplish? 

[Mara Finkelstein]

I am trying to archive issues that were created, never addressed and are no longer relevant or will not be addressed in the foreseeable future. I don't feel comfortable deleting them. Marking them as complete is incorrect.

[John Funk]

You should just create a Done status category status called Discarded or Aborted or something like that. Then you can move those cards to that status. 

[Brooklyn Stanley]

Is there really no movement to put an archive feature into the standard version? 

Looking at the differences between standard and premium, archiving is literally the only feature my company would use, but it's double the price. I hate feeling like the software I'm using is trying to manipulate me into purchasing higher packages than I truly need just to get features that should be standard. 

-- and developing a permission scheme is hardly a solution. It's a work around at best, and a tedious one at that.