Before You Archive Jira Projects: What Breaks, What Changes, and How to Prepare

Introduction

1) Two Very Different “Archiving” Approaches

• Jira built-in archive (Cloud/DC): Marks project/issues as archived. They’re hidden from most views, removed from the search index, and blocked from changes. Data and attachments remain in Jira and can be unarchived later. Faster searches due to a smaller index, but no storage reduction.

• Export-and-delete (e.g., Issue Archiver app): Creates a human-readable HTML snapshot with attachments and then deletes issues and files from Jira. Irreversible. Frees disk space and simplifies Cloud migration, but you can’t bring issues back into Jira later.

2) What Can Break Or Change After Archiving

2.1 Search, Filters, Boards, and Dashboards

• JQL and saved filters that reference the archived project will return fewer or zero results. Filter-based subscriptions may send empty emails.

• Agile boards (Scrum/Kanban) and backlogs scoped to the project will appear empty or error if exclusively tied to the archived project.

• Dashboards/gadgets driven by those filters will show lower counts or blank states. If a gadget is tightly bound to the archived project filter(s), expect empty visuals.

• Cross-project filters will exclude archived issues by design, potentially changing KPI/OKR trends.

2.2 Automations, Integrations, and Triggers

• Automation rules with project scope will stop firing; global rules with JQL that includes the project will ignore archived issues.

• Webhooks/integrations receiving events from that project will no longer receive updates.

• Email handlers or incoming mail that create issues in the project will fail or be rejected.

2.3 Links, Dependencies, and References

• Issue links pointing to archived content will still reference the key, but users may not be able to open the target in normal views.

• Confluence pages, runbooks, or external docs that deep-link to project issues will appear broken to end users (hidden or deleted depending on approach).

• Roadmaps (Advanced/Plan) and cross-project views will lose visibility of archived work, affecting capacity or dependency maps.

2.4 Notifications and Subscriptions

• Notification schemes stop sending events because archived projects do not generate activity.

• Filter subscriptions tied to archived issues will send emptier reports; consumers might think something is wrong with data pipelines.

2.5 Schemes and Shared Configurations

• Built-in archive keeps schemes in place. If you later delete the archived project, shared schemes might be affected if you attempt to clean them up. Verify sharing before deleting.

• For Team-managed projects (Cloud), configs are isolated; archiving/deleting has less risk of collateral impact on other projects, but migrations or backups can be impacted if you mix types.

2.6 Storage and Attachments

• Built-in archiving does not remove attachments; storage cost and backup times remain unchanged. Thumbnails and backups still consume space. See: How many disk space does a Jira attachment use actually.

• Export-and-delete removes attachments from Jira, reducing storage and backup windows. But this is a permanent removal from the live system.

2.7 Reporting, Audits, and Compliance

• Historic trend reports and gadgets relying on active issue data will change immediately after archiving/hiding content.

• If you later delete custom fields or options, then unarchiving might surface missing historical values (DC note). Snapshots avoid this by freezing values at archive time.

3) Preparation Checklist (Strongly Recommended)

4) Built-in Archiving: What To Expect (Cloud/DC)

• Reversible: You can unarchive, but any subsequent configuration cleanup (e.g., deleting custom fields/options) can cause value loss on unarchive in DC.

• Performance benefit: Reduced index size speeds up search. No reduction in file storage.

• User experience: Archived items disappear from most lists and pickers. JQL generally excludes archived by default.

Housekeep attachments before archiving to reduce long-term storage, backups, and migration payloads. See: Why do people housekeep attachments on Jira?.

5) Export-and-Delete Archiving (Snapshots)

• Irreversible: Issues removed from Jira cannot be reimported from the HTML snapshot.

• Storage reduction: Attachments and thumbnails are deleted from Jira; backups become faster and smaller.

• Audit-friendly: HTML snapshots capture a point-in-time record. Ideal when you need a fixed baseline or to exclude projects from Cloud migration while keeping an offline copy.

6) Communication Plan Templates

7) Safe Execution Steps

1. Take evidence and backups: Export key dashboards, save audit snapshots, and (DC) schedule backups as per policy.

2. Attachment strategy: Housekeep or export as needed; confirm legal/compliance retention windows.

3. Pilot: Archive a small set; validate searches, automations, and dashboards.

4. Archive: Perform the archive action (built-in or export-and-delete) during a low-traffic window.

5. Post-checks: Confirm board visibility, SLA dashboards, subscriptions, and webhook silence are as expected. Update documentation and Confluence links.

8) Frequently Asked Questions

9) Practical Tips and Good Practices

• Label and group filters/dashboards by project so they are easy to find and deprecate after archiving.

• Remove or rename legacy dashboards with status tags like “(Deprecated)” to reduce confusion.

• Batch large archives to minimize performance impact; monitor logs for timeouts or permission errors.

• Record ownership for filters, boards, and dashboards to streamline communications and approvals.

References

• Differences between Jira DC issue archiving and Issue Archiver

• Issue Archiver

• How many disk space does a Jira attachment use actually

• Why do people housekeep attachments on Jira?