Overview and setup
The fourteen tools, how they all work the same way, and what to do first.
What it is. A collection of separate tools on one admin page. You use one at a time. No tool runs on a schedule and none runs by itself — every one of them waits for you to click it.
Why it exists. Every Jira administrator has jobs that take hours because Jira has no screen for them: finding out which of 1,900 custom fields are actually used, merging two fields that mean the same thing, transferring everything a leaver owned, working out which schemes nothing references any more.
Who uses it. A Jira administrator. Some operations additionally need a site administrator, and the tool tells you when Jira refuses.
Admin Tools
Jira administration utilities.
The fourteen tools
| Group | Tool | What it does |
|---|---|---|
| Projects | Projects Manager | Every project in one table. Edit names, keys and leads inline; archive and restore in bulk. |
| Projects | Project Activity | Issue creation per project over 12 months, so you can tell live projects from dormant ones. |
| Configuration | Unused Schemes Cleanup | Finds 16 kinds of unused configuration object — schemes, and also the workflows, statuses, screens, field configurations, work types, priorities and resolutions inside them — and deletes the ones you select. |
| Configuration | Custom Fields Health Assessment | Grades every custom field for cleanup, duplication, naming, searchability and option quality. Exports CSV and PDF. |
| Configuration | Custom Field Merger | Merges duplicate fields: generates the CSV import for the values and replaces the field on every screen. |
| Configuration | Field Screens Migrator | Swaps one field for another on every screen where it appears, in the same tab at the same position — then offers to trash the old one. |
| Configuration | Filter Management | Audits every listable saved filter and how it is shared. Bulk reassign, unshare, and find-and-replace inside the JQL. |
| Configuration | Scheme Deduplication | Compares eleven kinds of scheme and groups the ones with identical settings, so you can consolidate them. Report only. |
| Configuration | Workflow Health | Scans workflows for bad practice: oversized ones, statuses nothing can reach, and start and end statuses in the wrong category. Report only. |
| Users | Mirror User | Copies groups and project roles from one person to another, then verifies the result. |
| Users | User Analysis | Turns the two CSV exports from admin.atlassian.com into a licence, activity and security report, with drill-down lists you can download. |
| Users | User Offboarding | Finds everything a departing person owns and transfers it to a replacement. |
| Migration | Migrated Fields Cleaner | Removes “(migrated)” from field names, descriptions and configurations. |
| Migration | Migrated Project Roles Cleanup | Removes “migrated” from role names and moves the members back into the original roles. |
Every tool works the same way
The pattern is deliberate: nothing changes until you have seen what will change.
- 1Scan. The tool reads your configuration in the background and shows progress. On a large site this takes minutes, not seconds.
- 2Review. Results come back as a table you can inspect and filter. Many tools show the current value next to the value after the change.
- 3Select. You tick the rows to act on. Nothing is selected for you.
- 4Apply. The action runs in the background and reports what succeeded, what was skipped and what failed.
- 5Start Over resets the tool so you can run it again with different settings.
What you need first
- Jira Cloud and Jira administrator rights.
- For group membership changes: a site administrator. This is an Atlassian restriction, and no app can work around it.
- For User Analysis: the CSV exports you download from admin.atlassian.com. The app reads files you provide, so it needs no organisation API key.
- An active app licence for anything that starts work. Reading, exporting and recovering stay available without one — see below.
What happens without an app licence
Twenty-six resolvers are gated, and they are all of one kind: the ones that start a scan or write to Jira. Everything else is deliberately left open, because locking an administrator out of results they already have — or out of the button that clears a stuck job — turns a lapsed subscription into a support ticket.
- Results you already have stay readable, in every tool, along with their CSV and PDF exports — those are generated in your browser from data already fetched.
- Every user, group, project and field picker still searches, so you can look something up.
- Cancel and start over works in every tool. A job interrupted on the last day of a trial does not leave you stuck.
- User Analysis works in full. It parses the CSVs you drop into it in the browser and calls no resolver at all, so it has no licence gate.
An unlicensed installation shows a warning at the top of the page — “This app does not have an active licence” — and greys out the buttons that start work, each with a line under it saying why.
Where to start
Run Project Activity and Custom Fields Health Assessment, in that order. Neither changes anything, and between them you get the two facts that drive every cleanup decision: which projects still matter, and which fields are dead weight.
- 1Install the app and open Jira → Apps → Admin Toolkit.
- 2Run Project Activity. Export the CSV. You now know which projects are dormant.
- 3Run Custom Fields Health Assessment. Export the PDF. You now have the cleanup case in writing.
- 4Pick one finding and act on it with the relevant tool. Do not try to fix everything in one session.