Archiving vs Deleting projects in Jira (ACP-120 Exam Topic)

Many teams treat deletion and archiving in Jira as similar actions, yet they serve very different purposes. Deleting a project is permanent.

Once the deletion is confirmed, that project and all of its issues, attachments, workflows, and history disappear from Jira.

The only recovery path is a full system restore from backup, which affects the entire environment. This is why deletion requires administrative caution and strong governance.

Jira Archives and Space Deletion

Archiving is designed for projects that are inactive but still important.

When a project is archived, it is hidden from daily operations and cannot be modified, but nothing is removed. Every issue, comment, attachment, workflow, and permission remains fully preserved. Administrators can unarchive the project at any time, bringing it back exactly as it was.

There are also rules about naming. When a project is archived, its key and name remain locked.

[embed]

No new project can reuse them until the archived project is unarchived and later deleted.

The differences matter to teams managing large portfolios. Archiving is ideal for long running initiatives that cycle between active and inactive phases.

Jira Certification Exam Topics

Deletion is useful only when a Jira project’s data has no future relevance.

Cameron McKenzie is an AWS Certified AI Practitioner,Machine Learning Engineer,Solutions Architect and author of many popular books in the software development and Cloud Computing space. His growing YouTube channel has well over 30,000 subscribers.

[embed]