Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Question on Archiving old issues and projects

I have been given the task to clean up our system for unused workflows/projects and issues older than 3 years old. I have a few questions about archiving and my searches were bringing up mixed information. Using Jira Server. Thanks for any help!

1) Are archived Jira issues searchable and reviewable by anyone?

2) Is archiving completed at project level or ticket level?

3) Can an archived issue/project be activated again?

4) If a workflow is deleted, will that delete archived projects?


1 answer

0 votes
Peter-Dave Sheehan
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 16, 2020

I do not believe there is any real archive option for Jira Server. This is a datacenter functionality only.

What we do is "archive" (big air quotes) at the project level. When a project is no longer used, we apply a special permission scheme that will hide the issues from everyone but administrators.

But the issues are still in the system, still using up space, still being indexed. But at least they don't clutter the user's experience.

The next step (which I've never actually taken) is to do a full xml backup of your instance and archive the XML with some attribute indicating that this xml is to archive that project. Then you would delete the project completely (all the issues will be gone and can't be searched). Should you need to view that project data in the future, you should be able to reimport just that project from your full instance xml.

As for workflow cleanup... just delete all "inactive" workflows. Those are backup and old copies of workflows that are not loner associated with any issue/project. Those are safe to delete.

You can't delete any workflows for projects archived using the fake permission-level archive as I described. Only after the project has been fully deleted (and the workflow is not shared) can you consider deleting the workflows.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events