Nothing is left behind.

Successor finds everything a departing person still owns in Jira, moves what Jira lets an app move to whoever takes over, and turns the rest into a tracked checklist - with a CSV record of what moved, what did not, and who signed off.

What it checks

A scan walks fifteen places where ownership hides. It is read-only: nothing changes until you confirm.

• Issue assignee
• Issue reporter
• Watchers
• Filter owner
• Dashboard owner
• Component lead
• Project lead
• Project role actors
• Notification recipients
• Permission grants
• JSM approvers
• Board admins
• Board-backed filter
• Groups
• Automation rules

Why it exists

Deactivating an account is the easy half. The half nobody sees is what the account was still holding: filters that boards depend on, dashboards nobody else can edit, approval steps that quietly stop, scheme entries routing alerts to an inbox that will never be opened again. None of it announces itself. It surfaces weeks later as a board that stopped returning results, or a request that never moved.

Successor asks one question - who is leaving, and who takes over - and answers it with a list, an action, and a record.

Where it runs

Successor is an Atlassian Forge app. It runs entirely on Atlassian infrastructure and makes no network calls outside your Atlassian instance. There is no server of ours for your data to travel to, because there is no server of ours.

Support

support@rigelapps.dev - attach the audit CSV from the run if you can; it carries the run ID and everything the app saw. Initial response within one business day.