Jira · Orphaned-Owner Cleanup
Every filter, dashboard, issue, and project lead still pointing at deactivated users. Runs entirely on Atlassian.
Runs entirely on Atlassian Forge inside your own tenant. No external servers, no data egress.
Deactivating a user closes their access but cleans up nothing they owned. Filters go un-editable, dashboards go unowned, issues stay assigned to ghosts, and projects keep leads who left a year ago. Jira has no report that surfaces any of it.
Built on Atlassian Forge: the app runs on Atlassian's own serverless platform inside your tenant, stores its data in Forge storage, and makes no external network calls. Every scope it requests, and why:
| read:jira-user | finding deactivated accounts |
| read:jira-work | filters, dashboards, issues, and project leads |
| storage:app | the cached queue, in your tenant |
No. The app runs on Atlassian Forge inside your own tenant with zero external egress, which makes it eligible for Atlassian's "Runs on Atlassian" trust marker.
Through the Atlassian Marketplace, on your existing Atlassian bill, priced per user like any Cloud app. The listing has a free evaluation and the exact calculator for your tier.
Email support@llmgraph.ai or open an issue from the documentation page. You talk directly to the people who build the app.
Free evaluation from the Marketplace listing. If it does not fit your workflow, tell us what would and we will build it.