How to Archive a Jira Project: 6 Steps, Tips & Checklist
Need to archive a Jira project without losing its history? This jira archive project guide gives you 6 steps, tips, and a checklist. Read now.
Old Jira projects can clutter your workspace, make project lists harder to scan, and leave teams unsure which work is still active. Keeping finished projects open may also create confusion about ownership, access, and where new work belongs.
But here's the truth: archiving is different from deleting. A careful archive can take a completed project out of everyday use while retaining its history for future reference. The exact controls vary between Jira Cloud and self-managed editions, so rushing through the process can lead to surprises.
Here’s a practical six-step guide to archiving a Jira project safely. You’ll learn what to check first, how to archive it, how to confirm the result, and what to do if you need the project again.
How to Archive a Jira Project in 6 Steps
In short, review the project, notify its stakeholders, check integrations and permissions, then use Jira’s archive control. Confirm the project is no longer active and make sure the right people know how to request access or restoration.
-

1. Confirm the project is ready to archive
Check that the work is complete or paused indefinitely. Review open issues, unresolved approvals, upcoming releases, and any work that still has an owner.
For example, if a release issue is still waiting for sign-off, settle it or assign a clear follow-up before archiving. A project with unresolved work may be better paused than archived.
-
2. Check your Jira edition and permissions
Jira’s menus and archive controls can vary by edition, version, and administrator settings. Confirm whether you use Jira Cloud or a self-managed Jira instance, then check the current project administration options.
You may need project administration or Jira administrator permissions. If you cannot see the archive control, ask your Jira administrator rather than changing permissions just to complete the task.
-

3. Notify people and check connected work
Tell project members, stakeholders, and support teams when the project will be archived. Include the project name, the planned date, and who they should contact if they still need access.
Also check whether the project connects to automations, dashboards, integrations, or recurring reports. A release dashboard or external service may need an update when the project leaves active use.
-
4. Review project details and access needs
Confirm the project name, key, owner, and purpose are clear enough for someone to recognize later. Check whether any team needs ongoing access to its issues or history.
If people need occasional reference, explain how they can request access or restoration. This simple step can prevent confusion when a past decision or issue becomes relevant again.
-
5. Archive the project using Jira’s controls
In Jira Cloud, project administrators commonly find the archive action through the project list or project settings. In self-managed editions, the option may appear in project administration or Jira administration.
Open the correct project, verify its name and key, and select the archive action available in your instance. Read any confirmation message before proceeding, since the interface and resulting access behavior can differ by version.
-
6. Verify the archive and record the next step
Return to the project list or administration area and confirm the project is marked as archived or no longer appears among active projects. Check relevant dashboards and integrations for unexpected changes.
Tell stakeholders that the archive is complete. Share the project owner or restoration contact, and note any follow-up needed for reports, automations, or access requests.
Archiving a Project Is Different From Deleting It
Archiving generally takes a project out of active use while retaining its project history. Deleting is a more destructive action that can remove project information, depending on the Jira edition and configuration.
Here's why the difference matters: a completed product launch may still provide useful context when a team plans its next release. Archiving can reduce clutter without treating that history as disposable.
Before acting, read the confirmation screen and verify what your Jira setup will retain. If you are unsure whether the project may be needed again, pause and check with your Jira administrator.
What to Check Before You Archive
A short pre-archive review can prevent avoidable interruptions. Start with unresolved work, ownership, and access; then consider the systems that rely on the project.
- Review open issues, pending approvals, and planned releases.
- Confirm a project owner or contact for future questions.
- Tell team members and stakeholders when the change will happen.
- Check dashboards, reports, automations, and integrations connected to the project.
- Confirm that anyone who needs future access understands the request process.
- Verify the project name and key before confirming the archive action.
For example, a service team might have closed all development tasks but still rely on an issue dashboard for quarterly reporting. Checking that dashboard first helps the team plan an alternative view or update its reporting process.
What Changes After a Jira Project Is Archived?
After archiving, the project is typically removed from active project views. Access to its issues and the way it appears in search, reports, or connected services may vary across Jira editions and configurations.
That means archiving can affect more than a project list. A dashboard that relies on an archived project may show different results, while an integration may stop behaving as expected if it depends on active project access.
Check the result with the people who rely on the project. If an important report or workflow changes, document the action in your team’s operating notes and decide whether to adjust the report or restore the project.
How to Restore an Archived Project
If the project is needed again, look for its archived status in the relevant project or administration area. Jira’s restoration options and labels depend on your edition, version, and permissions.
Ask a Jira administrator for help if you cannot find the restore control. Before restoring, confirm who needs access and whether the project’s owner, automations, integrations, or reports need attention.
The best part? A clear archive plan makes restoration easier to manage. Keep the project name, owner, and reason for archiving easy to identify, so the team can make a confident decision later.
Project Management Beyond Jira: ONES.com

Value proposition
ONES.com combines project management and knowledge management in one platform. ONES Project is a Jira alternative for project management, while ONES Wiki is a Confluence alternative for knowledge management; the products are sold separately.
Core capabilities
- Too many disconnected work steps: ONES Project brings project tasks and planning together, helping teams follow work in one project management environment.
- Workflows that do not match team practices: Custom workflows and fields let teams shape work stages and issue details around their processes.
- Limited visibility into delivery: Built-in reporting helps teams review progress and spot work that needs attention.
- Sprint planning needs: Sprint management supports teams that organize work into iterative development cycles.
- Repeated manual actions: Automation can reduce routine steps and help keep recurring workflows moving.
- Existing Jira habits: Jira-compatible workflows can make it easier for teams familiar with Jira to adapt their processes.
- Reliance on extra extensions: Native capabilities can reduce the need for plugins in workflows covered by the platform.
- Deployment restrictions: Teams can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment options.
ONES.com offers full feature parity between its cloud and self-hosted versions. That can help teams keep a consistent set of capabilities when deployment requirements call for a self-managed environment.
Application scenarios
A product team moving away from Jira could use ONES Project to manage issues, sprints, custom workflows, and reporting. It can assess the Jira-compatible workflows and native features it needs before deciding whether additional extensions are necessary.
A company with restricted network requirements could consider an On-Premise, Private Cloud, or Air-gapped deployment. A team that also wants a knowledge base can evaluate ONES Wiki separately, alongside ONES Project.
Common Challenges When Archiving Jira Projects
People cannot find a project they still need
Problem: Team members may expect an archived project to remain in their usual project list or search results.
Solution: Tell them the archive date and explain whom to contact for access or restoration. Include the project name and key in the notice.
A dashboard or integration changes unexpectedly
Problem: A report or connected service may rely on the project being active or accessible.
Solution: Check important dashboards and integrations before archiving. Afterward, verify that they still show the information your team needs.
The archive option is missing
Problem: Your account may not have the required permissions, or your Jira edition may place the control elsewhere.
Solution: Confirm your edition and ask a Jira administrator to locate the correct control. Avoid changing access settings without approval.
The team is unsure whether to archive or delete
Problem: The options can sound similar, even though their effects may differ significantly.
Solution: Review your retention needs and the confirmation prompt. When the project’s history may be useful later, check the archive option before considering deletion.
Frequently Asked Questions
Does archiving a Jira project delete its issues?
Archiving and deleting are different actions. Archiving generally removes a project from active use while retaining its history, but the precise access and retention behavior can depend on your Jira edition and settings. Check the confirmation message in your instance before proceeding. If your team has retention requirements, ask the Jira administrator to confirm how they apply to archived projects.
Can I archive a Jira project without administrator access?
That depends on the permissions configured in your Jira environment. Some archive actions require project administration or Jira administrator access, and the available controls can vary. If you cannot see the option, ask your Jira administrator to confirm your permissions and the correct process. Avoid requesting broader access than you need just to archive one project.
Can I restore an archived Jira project?
Many Jira setups provide a way to restore archived projects, but the route and permissions depend on the edition and version. Look in the project or administration area for archived projects, or ask a Jira administrator to help. Before restoration, identify who needs access and check whether dashboards, integrations, or automations need attention.
Will archiving affect Jira reports and dashboards?
It can. Reports and dashboards that rely on an archived project may display differently, depending on how they are configured and what the archive action changes in your instance. Check business-critical views before archiving and verify them afterward. If a report is affected, adjust its project scope or restore the project if continued access is necessary.
When should I archive a Jira project?
Archive a project when its work is complete or inactive, the team has reviewed outstanding issues, and stakeholders understand what will happen to access. Check connected reports and integrations first. If active work remains, or the team still depends on the project for routine tasks, resolve those needs before archiving or consider a temporary pause instead.
Conclusion
Archiving a Jira project can clear active project views while preserving a path back to its history. The key is to review unfinished work, permissions, stakeholders, and connected reports before using Jira’s archive control.
Then verify the result and make the next step clear for anyone who may need the project again. That simple process helps you reduce clutter without creating avoidable confusion or cutting off work the team still relies on.