What do you record before deleting an old Jira site or sandbox?

[Maya Lindholm]

I have been thinking about cleanup notes for old Jira sandboxes and test sites.

The deletion itself is usually not the hard part. The hard part is knowing later why the site existed, what was tested there, and whether anything useful was lost.

For a small sandbox, I like having a short cleanup note with:

- original purpose

- owner

- products/apps installed

- test data that matters

- links to any useful screenshots or findings

- whether anything should be recreated elsewhere

- final delete/cancel date

This feels especially useful when Marketplace apps or temporary trials were involved, because the billing/admin state can be separate from the work that happened inside the product.

For Jira admins who clean up old sites or sandboxes: what do you record before deleting them, and what have you regretted not recording?

[Maria Reisinger]

I like that your checklist focuses on the governance side, not just
the archive action itself.

One thing I keep thinking about: the checklist isn't usually the
difficult part. The difficult part is applying it consistently across
dozens or even hundreds of Jira projects.

At that scale, visibility becomes the real challenge. Questions like
these become surprisingly hard to answer with confidence:

• Which archived candidates are still referenced by dashboards, filters,
  automations, or Confluence pages?
• Which projects still show meaningful activity or user access?
• Is the project configuration actually dormant, or is it still evolving?

For transparency, I work on MetaFrazo, so this is a problem space I
spend a lot of time thinking about. I'm genuinely curious how other
organizations approach it.

Do you rely on governance processes, periodic
reviews, or some way of making these checks repeatable across your
Jira instance?

[Brita Moorus]

Good list! 👍 I'd also add:

• whether there are any integrations or webhooks pointing to the site

• any custom domains or DNS records

• API tokens, service accounts, or automation rules that might still reference it

• a final backup/export (if needed)

Those are easy to forget, but can save some head-scratching a few months later 😊