Admin Health for Jira Cloud
One scan shows the fields with no use it can find, the people who left but still own things, and the schemes and screens nothing uses. A second check shows the Jira limits you are about to hit. It only reads, and your Jira data never leaves your Atlassian site.
Join the free betaHow it worksPeople with no Jira access who still lead a space, are its default assignee, lead a component or own a filter. With a hand-over list.
Fields per space, statuses per workflow, work types, workflows per scheme and more, against Atlassian's own limits. Full and nearly full first.
Fields on no screen, in no filter and on no board, with when each last changed. Automation rules, workflows, request forms and apps are not checked, and the app says so: check them, and whether work items hold values, before you delete anything.
Workflows, schemes and screens with no known use, in the order they can be removed.
Permission settings that open spaces wider than you may intend, with a way to mark the ones you meant.
A page in each space's settings with that space's limits and leavers, and what to ask the Jira admin.
The app has read permissions only. It never changes your Jira. Every finding says what to check before you act.
It runs on Atlassian's own platform. Your Jira data is never sent to us or anyone else; we see only technical logs (codes and counts) that Atlassian shares unless your admin turns them off. Scan results delete themselves after 30 days; a mark you set on a finding is kept for a year.
We have run Jira for years. The app says plainly what it checked and what it could not, so you can trust what it does say.
Jira Cloud only. The beta is free. Read what the app reads and stores.
Factorant