Jira · Orphaned-Owner Cleanup

Find Jira filters, dashboards, and issues owned by deactivated users

Every filter, dashboard, issue, and project lead still pointing at deactivated users. Runs entirely on Atlassian.

Try it free on the Atlassian Marketplace Documentation

Runs entirely on Atlassian Forge inside your own tenant. No external servers, no data egress.

Why it exists

This app answers a request that has been open on Atlassian's public tracker for years: JRACLOUD-84210, "When removing a user, change the ownership of filters and dashboards instead of moving them to trash", with 65 votes. We wrote up the problem and the native workarounds on Atlassian Community.

The gap

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.

What it does

Finds every deactivated human account on the site, daily and on demand.
Flags saved filters and dashboards still owned by deactivated users.
Finds issues still assigned to, or reported by, deactivated users, site-wide.
Flags projects whose lead is deactivated.
Groups everything by artifact type and by departed owner, biggest first.
One-click, audit-ready CSV export of the full cleanup queue.

The cleanup queue: every orphaned artifact, grouped by type.

Per-owner rollup: which departed accounts left the most behind.

The daily scan sweeps filters, dashboards, issues, and project leads.

60-second walkthrough

Honest about its limits

The report is evidence, not action: reassignment happens through Jira's own admin screens, with the CSV as your worklist.
Only deactivated accounts are flagged. Active accounts never appear in the queue, however idle.
Read-only. This app reports and exports; it changes nothing in your instance.

Security & permissions

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

The native feature it builds on

Atlassian's own documentation for what Jira does out of the box, so you can see exactly where the gap is:

Deactivate a managed account (support.atlassian.com)

FAQ

Does any data leave my instance?

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.

How is it billed?

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.

Where do I get support?

Email support@llmgraph.ai or open an issue from the documentation page. You talk directly to the people who build the app.

Install Orphaned-Owner Cleanup in about a minute.

Free evaluation from the Marketplace listing. If it does not fit your workflow, tell us what would and we will build it.

Try it free Read the deep-dive