How to Archive a Jira Project: Step-by-Step Process [2026]
Need to archive a Jira project without losing vital history? Follow this 2026 guide to prepare, check access, and archive safely. Read now.
Closing a Jira project sounds simple until active issues, integrations, reports, or team responsibilities depend on it. Archive too early, and people may lose access to work they still need. Leave completed projects active, and they can clutter searches, boards, and project lists.
But here's the truth: archiving is usually a reversible way to retire a project without deleting its history. The key is preparing the project, checking your Jira plan and permissions, and confirming what changes after the archive. Here’s a step-by-step process you can use in 2026, with extra checks for Jira Cloud and Data Center. You’ll also learn when archiving makes sense, how to avoid common surprises, and what to do if the archive option is missing.
How to archive a Jira project safely
Use this sequence to confirm the project is ready, archive it through Jira administration, and check the result. Menu names can vary by Jira edition, plan, and permissions.
-

1. Confirm the project is ready to retire
Check with the project owner and the teams that rely on the project. Confirm that planned work is complete or has moved to an active project, and identify any issues that still need attention.
For example, if a support team still monitors a project’s unresolved bugs, agree on where those bugs will go before archiving. This prevents a completed initiative from hiding work that remains active.
-
2. Check your Jira edition, plan, and permissions
Project archiving availability depends on your Jira deployment, subscription, and administrator settings. You may need Jira administrator or organization administrator permissions. Ask your Jira administrator to confirm access before scheduling the change.
In Jira Cloud, eligible plans and current administrative settings determine whether archiving is available. Jira Data Center menus can also vary by version. If the option is missing, check your edition and permission level first.
-

3. Review project dependencies and integrations
Look for boards, dashboards, filters, automation rules, reports, and integrations that refer to the project. Note who owns anything that should be updated, paused, or retained.
For example, a dashboard may show a project’s open issue count to managers. If archiving changes what that dashboard can display, arrange a replacement view before the project is archived.
-
4. Agree on a handover and retention plan
Tell the project team when the archive will happen, who can answer questions afterward, and where related work will continue. Capture any important decisions, ownership details, or follow-up tasks in an approved team space.
Check your organization’s retention and access requirements before changing project availability. This is especially important when a project contains information that specific teams must be able to review later.
-

5. Open the project administration area
In Jira, open the project you plan to archive and look for its administration or settings area. Depending on your edition and interface, you may instead manage projects through Jira administration.
Review the project name and key before continuing. Similar names can make it easy to select the wrong project, especially when several projects share a team or product name.
-
6. Choose the archive action and confirm
Find the archive action in the project menu or project administration list. Review Jira’s confirmation message carefully, then confirm only after checking the project identity and timing.
If you cannot find an archive action, do not substitute deletion. Ask an administrator to check plan availability, permissions, and the instructions for your Jira version.
-
7. Verify the project’s archived status
Afterward, check the archived-project area or administration view available in your Jira edition. Confirm the intended project is archived and that the team understands how to request restoration or locate retained information.
Also review the dashboards, saved filters, and integrations you identified earlier. If anything still points to the retired project, update it or assign an owner to resolve it.
What Jira project archiving changes
Archiving retires a project from everyday work while preserving its history for later reference or restoration. The exact effect on visibility, search, and related Jira features depends on your Jira edition and configuration.
Think of an archived project as a closed branch of work. It is no longer part of the team’s active project list, but Jira may retain its issues and settings for administrators or restoration.
Here’s why the distinction matters: archiving is different from deleting a project. Deletion can remove project content, while archiving is intended to preserve the project in an inactive state. Check Jira’s confirmation details before you proceed.
When archiving is better than other options
Archiving fits a project that has finished and no longer needs day-to-day activity. A completed product launch, a finished migration, or a retired internal initiative may be good candidates.
For a project that still has active tasks, consider moving those tasks to a current project and assigning clear owners first. If the project is only temporarily quiet, leaving it active may be easier than archiving and restoring it later.
Deletion is a separate choice with different consequences. If your goal is simply to reduce clutter, compare archiving with project permissions, board filters, and clear naming conventions before choosing a permanent action.
Pre-archive checks that prevent surprises
Run through these checks with the project owner before confirming. A short review can catch dependencies that are easy to miss when a project appears finished.
- Work status: Confirm unresolved issues are complete, reassigned, or intentionally retained.
- Ownership: Name a person or team to handle later questions and restoration requests.
- Reports: Review dashboards, filters, and reports that depend on the project.
- Integrations: Check automation and connected services that may reference the project.
- Access: Confirm who needs historical access and whether archiving changes that access.
- Communication: Tell affected teams when the project will be archived and where work continues.
- Retention: Follow your organization’s rules for retaining project history.
For example, a software team may finish a release project but still use its issue history during support reviews. Checking the reports and access needs beforehand can prevent a scramble after the archive.
How to restore or review an archived project
If a team needs the project again, an administrator can check Jira’s archived-project area and available restoration controls. The exact route depends on the deployment and version, so follow the instructions shown in your Jira administration interface.
Before restoring, confirm why the project is needed and whether its old workflows, permissions, and integrations still fit. A project archived two years ago may have settings that no longer match current team practices.
After restoration, test a few key paths. Check that team members can access the project, issues appear where expected, and relevant dashboards or automation behave correctly.
Managing project transitions with ONES.com
ONES.com combines project management and knowledge management in one platform. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge base product and a Confluence alternative. They are sold separately.

For teams retiring Jira projects, ONES.com can support the work around a transition: organizing active tasks, maintaining team knowledge, and keeping workflows visible. It does not need to replace Jira archiving itself.
Core capabilities
- Pain: Teams need familiar issue workflows during a transition. ONES capability: ONES Project supports Jira-compatible workflows. Result: Teams can preserve a recognizable process while organizing ongoing work.
- Pain: Project status can become hard to follow after work moves. ONES capability: Built-in reporting provides project visibility. Result: Teams can review progress without relying on scattered status updates.
- Pain: A team’s process may not fit a default workflow. ONES capability: Custom workflows and fields let teams represent their own work. Result: Project tracking can reflect the steps and information the team needs.
- Pain: Sprint-based teams need to plan and review work consistently. ONES capability: ONES Project includes sprint management. Result: Teams can continue organizing iterative work in a familiar format.
- Pain: Repeated manual updates take time during project transitions. ONES capability: Automation can handle supported routine actions. Result: Teams can reduce repetitive coordination work.
- Pain: A growing collection of plugins can increase maintenance effort. ONES capability: Core project management features include reporting, custom workflows, fields, sprints, and automation. Result: Teams may reduce reliance on separate plugins for those needs.
- Pain: Some organizations cannot use a public cloud deployment. ONES capability: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Result: Teams can evaluate an option that fits their deployment requirements.
- Pain: Teams want to test project management without starting with a large rollout. ONES capability: The free plan supports up to 30 seats. Result: A small team can assess whether the workflow suits its work.
ONES.com offers full feature parity between its cloud and self-hosted versions. That gives organizations a way to consider deployment needs without treating self-hosting as a reduced-feature option.
Application scenarios
Jira project retirement: A team moves active work into ONES Project while keeping its Jira project available for the planned archive and retention process. The team can maintain current task ownership separately from historical project access.
Knowledge handover: A delivery team uses ONES Wiki to organize team guidance and project handover information while ONES Project tracks remaining work. Since the products are sold separately, teams can choose the product or products that fit their needs.
Restricted deployment needs: An organization evaluating project management for a protected environment can compare Air-gapped, On-Premise, Private Cloud, and Cloud deployments against its operational requirements.
Common challenges when archiving a Jira project
There is no archive option
Problem: The menu does not show an archive action. Solution: Ask a Jira administrator to confirm your permissions, subscription, deployment, and version. Avoid using deletion as a workaround.
Some issues are still active
Problem: The project looks finished, but unresolved work remains. Solution: Review each open issue with its owner. Complete it, move it to an active project, or record why it should remain available.
A dashboard or integration stops behaving as expected
Problem: A report or connected process depends on the project. Solution: Identify those dependencies before archiving, then update them or name an owner who can test and repair them.
People cannot find historical work
Problem: Team members assume archived issues are available in the same way as active project issues. Solution: Explain the expected access changes, point people to the right administrative route, and share the restoration contact.
Frequently asked questions
Does archiving a Jira project delete its issues?
Archiving is intended to retire a project while preserving its history, rather than delete it. The visibility and access behavior can vary by Jira edition and configuration. Read the confirmation message in your Jira interface, and check the project’s status afterward. If you need permanent removal, treat deletion as a separate decision.
Who can archive a Jira project?
The required permission depends on your Jira setup. In many organizations, a Jira administrator or project administrator handles the action, but local roles and settings can differ. If you cannot see the archive control, ask your Jira administrator to verify your access and whether your Jira plan supports project archiving.
Can I archive a Jira project that still has unresolved issues?
Jira may allow an administrator to archive a project with unresolved issues, but that does not mean those issues are ready to leave active work. Review each one with its owner. Move, complete, or deliberately retain outstanding work, and tell affected teams where they should continue tracking it.
Can I restore an archived Jira project?
Restoration is generally available through Jira administration, but the steps and permissions depend on your deployment and version. Ask an administrator to locate the archived project and check the available restore action. After restoring it, verify access, workflows, integrations, and reports before the team resumes work.
Conclusion
Archiving a Jira project is a practical way to retire completed work while preserving a path to its history. First confirm the project is ready, review dependencies and access needs, and check that your plan and permissions allow the action.
Then archive the correct project through Jira administration and verify the result. If open work, reports, or integrations still depend on it, resolve those needs before proceeding. A clear handover makes the archive easier for the whole team to live with.