Archive a Project in Jira: 6 Steps to Do It Safely Today
Need to archive a project in Jira without losing access or disrupting workflows? Follow 6 safe steps to preserve history and tidy your workspace. Read now.
Projects that look inactive can still contain decisions, issue history, and links your team relies on. Archive one too soon, and people may lose access or a connected workflow may stop working.
Leaving old projects active has its own cost. They clutter search results, confuse new teammates, and make it harder to spot current work. Deleting a project is even riskier when you only want to tidy up.
But here's the truth: archiving is usually a safer way to retire completed work while keeping it available for later reference. I’ll walk you through six careful steps, including what to check before you click, how to archive through Jira, and how to confirm the project is safely out of active use.
How to Archive a Jira Project Safely: 6 Steps
To archive a project, check its status and dependencies, notify its stakeholders, confirm your Jira permissions, then use the archive action in your Jira project list or administration area. Finish by checking that the project is archived and that your team can still find what it needs.
Jira’s menus and required permissions vary by product version and configuration. If you cannot find the archive action, ask a Jira administrator to confirm your access and available options.

1. Confirm the Project Is Ready to Retire
Check with the project lead before changing its status. Confirm that active issues are closed, transferred, or assigned to another project, and that no planned work still depends on it.
For example, a completed website redesign may still have open support issues. Resolve or move those issues first so archiving does not disrupt the people handling them.
2. Review Links, Boards, and Integrations
Look for workflows and tools that refer to the project. Check dashboards, saved filters, boards, automation rules, integrations, and recurring reports.
A filter that includes the retiring project may still be useful for historical reporting. Record its purpose and update any active views that should no longer include archived work.
3. Notify Stakeholders and Preserve Useful Details
Tell project members when the project will be archived and where related work will continue. Give them time to note important decisions, links, and follow-up responsibilities.
Keep essential project details in an approved knowledge area, especially if teams need them after access changes. Avoid moving information that is private or subject to retention rules without approval.
4. Confirm Your Permissions and Jira Version
Jira commonly restricts project archiving to administrators or people with specific administrative permissions. Ask your Jira administrator if the action is missing from your menus.
Cloud and self-managed Jira installations can present different routes. Confirm your product version and plan before following interface instructions meant for another environment.

5. Use Jira’s Archive Action
In Jira Cloud, an administrator may find the archive action in the project directory, often through the project’s actions menu. In other installations, look in project administration or ask an administrator to locate the equivalent option.
Check the project name and key before confirming. Jira may show a confirmation prompt, giving you a final chance to verify that you selected the correct project.
6. Verify the Archived State and Access
Return to the project list or administration area and confirm the project appears as archived. Check whether the interface provides a way to view or restore archived projects.
Ask a teammate to test the access they need, such as viewing historical issues or retrieving a link. If anything important is unavailable, pause further cleanup and contact your Jira administrator.
What Changes When You Archive a Jira Project?
Archiving generally removes a project from active project views while retaining it for administrative or historical use. The exact visibility and access rules depend on your Jira product, configuration, and permissions.
Here's why: archiving is different from deleting. A deleted project may be difficult or impossible to recover, while an archived project may be restorable by an administrator. Confirm the restoration process before proceeding.
For example, a finance team could archive last year’s expense-tracking project after closing its open issues. Team members can focus on the current year without immediately discarding prior issue history.
What to Check Before You Archive
Use a short readiness review to catch dependencies that are easy to overlook. This is especially useful when several teams share boards, reports, or automation rules.
- Project status: Confirm work is complete, transferred, or clearly assigned elsewhere.
- Issue ownership: Check that active issues have a responsible team and destination.
- Reporting: Identify filters and dashboards that include the project.
- Automation: Review rules that trigger on project activity or issue changes.
- Stakeholders: Tell affected people when and where work will continue.
- Retention: Check internal policies before changing access or preserving historical details.
A simple example: if a shared dashboard shows all projects with unresolved work, archiving a project may change its results. Decide whether the dashboard should continue to include historical issues.
Archiving, Deleting, or Leaving a Project Active
Choose the action that matches your goal. Archiving suits completed work you may need to revisit; deletion suits cases where removal is approved and appropriate; leaving a project active suits ongoing work.
Imagine your team has finished a product launch. If you expect questions about decisions or defects, archiving keeps a path to historical context. If the project still supports active maintenance, keep it available or move that work first.
You might be wondering: should you delete the project after archiving? Treat that as a separate decision. Check retention requirements, restoration options, and stakeholder approval before permanently removing anything.
Make Project Lifecycle Management Easier with ONES.com

Value Proposition
ONES.com combines project management and knowledge management in one platform, with ONES Project for project work and ONES Wiki for team knowledge. The products are sold separately, so teams can choose the capabilities that fit their needs.
If you are reviewing how your team manages old and active work, ONES.com offers a Jira alternative through ONES Project. Its deployment choices include Cloud, On-Premise, Private Cloud, and Air-gapped environments.
Core Capabilities
- Scattered project information: ONES.com combines project management and knowledge management capabilities, helping teams keep project work and team knowledge connected.
- Workflows that do not match your process: ONES Project supports custom workflows and fields, allowing teams to reflect their approval and delivery steps.
- Jira migration concerns: Jira-compatible workflows can make it easier to adapt familiar project practices when evaluating a Jira alternative.
- Manual progress reporting: Built-in reporting helps teams review project status without relying on a separate reporting add-on for every view.
- Unclear sprint progress: Sprint management supports planning and tracking work across development cycles.
- Repetitive task handling: Automation can reduce routine actions, giving teams more time for active project work.
- Plugin sprawl: Native capabilities can reduce reliance on multiple plugins for common project management needs.
- Restricted hosting requirements: Cloud, On-Premise, Private Cloud, and Air-gapped deployment options support different operating environments.
- Uncertainty about self-hosted features: ONES.com offers feature parity between its cloud and self-hosted versions.
Application Scenarios
A software team replacing a Jira setup can evaluate ONES Project for familiar workflows, sprint management, custom fields, automation, and reporting. The team can review which integrations and processes need adjustment before moving active projects.
An organization with strict network requirements can consider a self-hosted deployment, including an Air-gapped environment. It can also assess whether ONES Wiki would suit its knowledge management needs alongside ONES Project.
Teams exploring the platform can start with the free plan, which supports up to 30 seats. Assess the current project lifecycle, deployment requirements, and plugin needs before choosing a setup.
Common Challenges When Archiving Projects
People Still Need Access to Historical Issues
Problem: Team members discover too late that they cannot reach an archived project or issue.
Solution: Test access with a representative teammate before archiving. Tell the team how to request historical information and who can restore the project if needed.
Dashboards or Filters Stop Showing Expected Results
Problem: A report no longer includes a project after its status changes.
Solution: Review important filters and dashboards first. Update views meant for active work, and preserve separate historical reporting where it remains useful.
Open Work Gets Left Behind
Problem: An issue remains unresolved even though the team considers the project finished.
Solution: Review unresolved issues with the project lead. Close them when appropriate, or move them to an active project with a clear owner.
The Archive Option Is Missing
Problem: A project manager cannot see an archive action in Jira.
Solution: Ask a Jira administrator to check permissions, product version, and plan availability. Avoid using deletion as a workaround for missing archive access.
FAQs About Archiving Jira Projects
Can I restore a Jira project after archiving it?
In many Jira environments, an administrator can restore an archived project, but the exact process depends on your product and configuration. Before archiving, ask your Jira administrator where archived projects appear and who can restore them. If restoration is unavailable or restricted, treat the action as a significant access change and get approval first.
Does archiving a project delete its issues?
Archiving is intended to retire a project from active use, rather than delete it. However, visibility and access to its issues can differ by Jira version, permissions, and configuration. Confirm what project members can still view after archiving, and do not assume that archived issues remain visible in every board, search, or report.
Why can’t I find the archive option in Jira?
The archive action may be restricted to Jira administrators or specific roles. Its location can also differ between Jira Cloud and self-managed installations. Ask an administrator to check your access and confirm whether your Jira plan and version support project archiving. Do not substitute deletion unless the project owner has approved permanent removal.
Should I archive or delete a completed project?
Archive the project when you want to reduce clutter but may need its history later. Consider deletion only after checking retention rules, permissions, and the consequences for related issues and reporting. For a project that still supports active maintenance, transfer the work or leave the project available rather than treating completion of its original goal as the end of all activity.
Conclusion
Archiving can make Jira easier to navigate while preserving completed project history for future reference. The safest approach is to review open work, check dependencies, notify stakeholders, confirm permissions, and verify the result afterward.
But here's the truth: a single archive action can affect reports, access, and linked workflows. Take a few minutes to check those details before you proceed, and ask an administrator for help when the available options are unclear.
When you plan project retirement carefully, you can clear space for current work without rushing into deletion. If your team is reassessing its project management setup, compare the workflow and deployment needs against options such as ONES Project.