Quietfail Apps

Documentation

Offboarding Map for Jira and Confluence — install, scan, read, export.

Requirements

A Jira Cloud site where you are a Jira administrator. The app reads Confluence as well; if your organisation has Confluence on the same Atlassian organisation, install the app there too so it can read spaces and pages. The app never writes to Jira or Confluence — every call it makes is a read.

1. Install

Install from the Atlassian Marketplace listing. Installation asks a site administrator to grant the read scopes the app declares. There is no configuration step and nothing to connect: the app has no external service to point at.

2. Open the app

In Jira: Settings → Apps, then pick Offboarding Map for Jira and Confluence in the left sidebar. The app has three tabs — Person view, Object view and Scan.

3. Run the first scan

Go to the Scan tab and press Start scan. The scan builds the inventory that the other two tabs read; before it finishes, they have nothing to show.

How it works, and why it matters on a large site: the scan is sliced — one slice per Jira project, one per Confluence space, plus one for filters and dashboards. Each slice records its own receipt, so an interrupted run resumes instead of restarting, and re-processing never duplicates a row.

Press Refresh status to see progress. On a site with 704 projects and spaces the scan took about 50 minutes and found 4,906 dependencies. Duration grows with the number of projects and spaces, not with the number of users.

If a slice fails — the platform occasionally returns a transient error — the Scan tab names the slice and the reason. Press Resume scan to re-run what did not complete.

4. Person view — what breaks if I deactivate this person

Search by name or email and pick the person. You get every Jira and Confluence object that depends on them, grouped by product, object type and relationship, each group labelled CRITICAL, HIGH, MEDIUM or LOW.

What the levels mean:

App accounts and portal customers are excluded from the inventory. On a seeded test site they were half of every relationship found, and nobody offboards Automation.

5. Object view — who depends on this object

The reverse question. Enter a project id, space id, filter id or dashboard id and see every person attached to it, with the same risk scale. Useful before archiving a project or a space.

6. Export to CSV

Export CSV in Person view exports that person; Export all (CSV) on the Scan tab exports the whole inventory. Copy the contents of the box, paste into a text editor and save with a .csv extension and UTF-8 encoding. The screen tells you how many lines the saved file must have, so you can check the copy succeeded.

Columns: Person, Product, Type, Object Name, Scope, Relation, Risk Level, Account ID. The Risk Level column uses the same scale the app shows on screen. The first line is a sep=, directive, which makes Excel open the file in eight columns in any locale — without it, a comma-separated file lands in a single column wherever the list separator is a semicolon.

What this version does not do

Data and privacy

Everything the app stores lives in Forge storage, provisioned by Atlassian and scoped to your installation. Scan results are replaced on each new scan, and uninstalling the app removes all of its storage. Full detail in the privacy policy.

Support

Email [email protected]. Response within 5 business days.