How to Archive a Project in Jira: 6 Steps and a Checklist
Need to tidy Jira without losing project history? Learn how to archive a project in Jira safely with 6 steps and a checklist. Read now to get started.
An old Jira project can clutter project lists, confuse reports, and make active work harder to find. Yet archiving the wrong project can interrupt access, dashboards, automation, or integrations that still depend on it. Deleting a project to clean up quickly can also put important history at risk.
You can archive a Jira project while keeping a path to restore it later. The key is to confirm the project is inactive, check its dependencies, and verify the result afterward. Jira’s menus and permissions can vary by product version, so I’ll show you what to check before you act. Here’s a six-step process, followed by a practical checklist for archiving with fewer surprises.
How to archive a project in Jira: six steps
To archive a Jira project, confirm your permissions, review the project and its dependencies, notify affected people, archive it through Jira’s project controls, and verify that it is no longer active. Keep a recovery plan so an administrator can restore the project if needed.
Jira’s interface can differ between Cloud and self-managed installations, and it may change over time. If the menu names below do not match your screen, look for the project’s actions menu or ask a Jira administrator to confirm the current process.
-

Confirm that you have permission to archive projects
Check that your account has the Jira administration rights required for project archiving. If you cannot see the archive action, ask a Jira administrator to confirm your permissions rather than trying to work around them.
For example, a project lead may be able to manage project settings without having the site-level rights needed to archive the project. Settling this first avoids a last-minute handoff.
-
Identify the right project and confirm it is inactive
Verify the project name, key, owner, and current status. Then check for unresolved issues, active sprints, recent updates, and work that still needs a team’s attention.
A project with no recent activity might still support a release, audit, or customer commitment. Ask the project owner to confirm that active work has moved elsewhere before you proceed.
-
Review project dependencies and access needs
Check whether dashboards, reports, automation rules, integrations, or team processes refer to the project. Also consider whether people still need to consult its issue history.
For example, a support team may use an old project’s issues when investigating recurring incidents. Record any important links or reporting needs, and agree on another way to find that history if necessary.
-
Notify affected people and agree on timing
Tell the project owner and affected teams when you plan to archive the project. Include the project name and key, the reason for the change, and who to contact if someone spots a dependency.
Choose a time that avoids a busy release or reporting deadline. A short notice period gives teams a chance to flag overlooked work before project access changes.
-
Archive the project in Jira
Open Jira’s project directory or project administration area, find the project, and open its actions menu. Choose the archive option and confirm the action when Jira prompts you.
The exact route depends on your Jira edition and interface. If the option is missing, stop and ask an administrator to check the supported procedure for your installation. Avoid deleting the project as a substitute for archiving.
-
Verify the archive and record the recovery route
Return to the project list and confirm the project is marked or treated as archived. Check that affected users understand how the change affects their work, and look for issues with reports or integrations.
Record who can restore the project and how to request restoration. If your organization has a retention or change-management process, note the archive date and project owner there.
What archiving changes in Jira
Archiving is intended to move a project out of active use while preserving a route to recover it. It can reduce clutter in project navigation and help teams focus on current work.
However, the experience of an archived project may differ from an active one. People may no longer find it through their usual project lists or searches, and reports, integrations, or routines can behave differently if they rely on it.
Here’s why checking the impact matters: an archived project can still be valuable for historical reference. A team reviewing a past release, for instance, may need its issues even though it no longer plans new work there.

Pre-archive checklist for a safer change
Use this checklist before you archive. It turns a quick administrative action into a change your team can understand and reverse when needed.
- Project identity: Confirm the project name, key, owner, and intended destination.
- Work status: Check for open issues, active sprints, planned releases, and unresolved commitments.
- Dependencies: Review dashboards, reports, automation, integrations, and team routines that refer to the project.
- People: Notify the owner and anyone who still needs to consult the project’s history.
- Timing: Avoid archiving during a release, audit, or important reporting period.
- Recovery: Confirm which administrator can restore the project and how people should request it.
- Verification: Plan to check project visibility and connected processes after archiving.
The best part? This review can be brief. For a small project with no open work or integrations, a few checks may be enough. A project tied to shared reports needs a closer review.
When to archive, and when to choose another approach
Archiving is a good fit when a project has finished its work and the team wants to preserve its history without keeping it in the active project area. A completed campaign or retired product initiative can be a clear candidate.
If work is still underway, consider closing or transitioning issues instead. If people need frequent access, the project may belong in an active state with clearer ownership or organization. Deletion is a separate, more consequential action; confirm your retention and recovery needs before considering it.
You might be wondering: what if the project is inactive but still supports occasional reporting? Check whether the reports can be updated to use an appropriate alternative before archiving. If that change would make the history difficult to access, keep the project available until the reporting need is resolved.
How to handle access and restoration after archiving
Tell people what changed and where to ask for help. A short message can explain that the project is archived, identify its owner, and provide the administrator contact for restoration requests.
If someone later needs the project, ask an administrator to assess the reason and restore it through the supported Jira controls. After restoration, check project visibility and any connected reports or automation before relying on it again.
Let me explain: restoration is most useful when the recovery path is known in advance. For example, a team that archives an old launch project can record its key and administrator contact, making a later review much easier.
Project management beyond Jira: ONES.com
ONES.com brings project management and knowledge management together on one platform, powered by ONES Assistant. ONES Project is a Jira alternative, while ONES Wiki is a Confluence alternative; they are sold separately.

If you are reviewing how your team manages project lifecycles, ONES.com offers another environment to consider. Its deployment choices and built-in project capabilities may suit teams looking to manage workflows with fewer added plugins.
Core capabilities
- Fragmented project and knowledge work: ONES.com combines project management and knowledge management on one platform, helping teams connect work planning with team knowledge.
- Jira workflow familiarity: ONES Project supports Jira-compatible workflows, helping teams move established processes into a Jira alternative with less workflow disruption.
- Limited reporting visibility: Built-in reporting helps teams review project progress without relying on a separate reporting add-on for every view.
- Rigid processes: Custom workflows and fields let teams adapt project tracking to their own review stages and information needs.
- Sprint planning needs: Sprint management supports teams organizing iterative work and tracking progress through planned cycles.
- Repeated manual tasks: Automation helps reduce repetitive work in project processes, freeing teams to focus on decisions and delivery.
- Plugin complexity: Native capabilities can reduce the need to assemble multiple plugins for common project management needs.
- Deployment constraints: ONES.com is available as Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with full feature parity between cloud and self-hosted versions.
ONES.com offers a free plan for up to 30 seats. The deployment options can matter to teams with specific hosting or network requirements, including organizations that need an air-gapped environment.
Application scenarios
A team transitioning from Jira: A team that wants Jira-compatible workflows can evaluate ONES Project’s workflow, reporting, sprint, custom-field, and automation capabilities. It can compare the fit against its current process before deciding whether to move.
A team with restricted hosting requirements: An organization that cannot use a public cloud service can assess On-Premise, Private Cloud, or Air-gapped deployment options. The team can also review the stated feature parity across cloud and self-hosted editions.
A team managing project work and knowledge separately: A team can consider ONES Project for project management and ONES Wiki for knowledge management. Because the products are sold separately, it can assess each need independently.
Common challenges when archiving a Jira project
- The archive option is missing. Your account may not have the required administrative permission, or your Jira edition may use a different route. Ask a Jira administrator to confirm the supported process.
- A report stops showing expected results. The report may depend on active project visibility or a specific project reference. Review its configuration and decide whether the report should include another active project or use a different approach.
- A team needs the project after it is archived. Ask an administrator to review the request and restore the project when appropriate. Share the project key and the reason access is needed to speed up the assessment.
- An integration or automation behaves unexpectedly. Check whether the rule or integration refers to the archived project. Update its configuration only after confirming the intended workflow with its owner.
- People mistake archiving for deletion. Explain the difference before the change. Tell the team that archiving changes active availability and that an administrator can assess restoration requests.
Frequently asked questions
Does archiving a Jira project delete its issues?
Archiving is intended to take a project out of active use, rather than serve as a deletion action. The exact access and visibility effects can depend on your Jira edition and configuration. Check your organization’s retention requirements and test the expected behavior with an administrator before archiving an important project. If you need permanent removal, treat that as a separate decision and confirm its consequences first.
Who can archive a project in Jira?
Project archiving generally requires administrative rights, and a project lead may not have enough permission to perform it. The specific permission requirements can vary by Jira edition and configuration. If you cannot see the archive control, contact a Jira administrator and ask them to confirm both your access and the correct route for your environment.
Can an administrator restore an archived Jira project?
Jira provides a restoration path for archived projects in supported configurations. Ask an administrator to locate the archived project and use the appropriate restore control for your edition. After restoring it, verify project visibility and check any reports, integrations, or automation that might have been affected. Keep the project key and owner details available so the administrator can identify the right project.
Should I archive a project with open issues?
Pause and review the open issues before archiving. Confirm who owns each item, whether work needs to move to another project, and whether any deadlines or commitments remain. For example, an unfinished maintenance issue may need a new owner and destination. Once open work has a clear plan, the project owner and administrator can decide whether archiving is appropriate.
Conclusion
Archiving can clear inactive projects from active Jira work while preserving a recovery path. Confirm permissions, check project activity and dependencies, notify affected people, use Jira’s archive controls, and verify the result.
But here's the truth: the few minutes spent checking dashboards, integrations, and open work can prevent a frustrating interruption later. Use the checklist, record how restoration works in your environment, and archive only when the project’s next chapter is clear.