Governed administration for Jira Cloud
Admin Ops for Jira® gives administrators the offboarding, bulk-edit and housekeeping tools a growing instance needs, with a preview, a confirmation and an audit record for every change. Nothing changes until you have seen it.
Free for up to 10 users. Billed through your Atlassian account.
What it does
Move a leaver’s filters and dashboards to a new owner, remove group access without deleting the account, and find the grants held by one named person.
Find what Jira cannot show you: schemes identical in content, custom fields nobody fills in, screens nothing references, filters saving the same query.
Label, set a field, transition, move or delete issues by JQL through Jira’s native bulk API, acting on exactly the issues the preview showed.
Safety model
Whether a label goes onto 400 issues or five schemes become one, every tool that changes something follows the same three steps.
A dry run lists every affected object with what the decision depends on: query, shares, favourites, last use. Every row can be deselected. Nothing in Jira changes.
Anything irreversible opens a dialog that names each object and lists what stops working afterwards. It runs only after you type a word.
The server re-derives the objects and acts on the set the preview pinned. The log records who started what, and the outcome for each object.
Filters have no trash in Jira. A deleted filter cannot be restored.
Features
Every screen states its effect beside its heading. Half of them only read, so an instance can be reviewed before anything changes.
One view across every audit, for the question an administrator asks first: does anything need attention right now?
Who can reach what, and what happens to the objects of someone who leaves, including the Jira Service Management customers and organizations behind a portal.
What piles up over the years, who owns it, who still uses it, and what breaks if it goes.
One JQL query, one operation, applied through Jira’s own asynchronous bulk API.
Jira Cloud allows 700 custom fields and slows down well before that. Both screens reduce the count without losing data.
What remains when projects and workflows are retired, who among your administrators may use the app, and the record of everything it has done.
For enterprise administration
Admin Ops does not widen what administrators can do. It makes the work faster, and every step visible, reviewable and attributable.
Assign auditor (read only), operator (read and change) or owner to named administrators. Enforced on the server for every request, and every policy change is logged.
The preview names every object and makes a sound attachment to a change ticket. The log is the evidence afterwards. The app does not pretend to be an approval workflow.
Every change appears in the app’s log, in Jira’s own audit log and in issue history, always under the administrator who ran it.
Scans run in slices and resume, so a large instance costs time rather than completeness. Caps are reported, never applied silently.
Security & compliance
Admin Ops runs entirely on Atlassian Forge. There is no vendor infrastructure in the path, and we as the vendor never receive your data.
| Question | Answer |
|---|---|
| Where does the app run? | Entirely on Atlassian Forge, inside your Atlassian tenant. |
| Does any data leave Atlassian? | No. The app declares no external endpoints and makes no external calls. |
| Are there sub-processors? | None. No data is sent anywhere. |
| Does the app hold privileges of its own? | No. Every call runs as the administrator using it, so Jira’s permissions always apply. |
| What is stored? | An audit log of the 50 most recent runs, the access policy and a ten-minute preview set, in Forge storage inside your tenant. |
| What happens on uninstall? | All stored data is removed. There is no vendor-side copy. |
Use cases
Each guide follows the order that loses no information, using the screens the app provides for it.
Offboard a departing user without losing their filters and dashboards.
Read moreGet your custom field count down, without deleting anything that holds data.
Read moreFind permission schemes that differ only in name, and consolidate them.
Read moreLabel, transition, move or delete hundreds of issues by JQL, safely.
Read moreCopy a team’s dashboard for another team, with its filters rewritten.
Read moreGuides for every screen, limits and result codes, the safety model and the enterprise rollout.
Read morePricing
Small instances
Free
On Jira instances with up to 10 users, with every feature.
From 11 users
Per user
A tiered price per user and month, with the unit price falling as your user count grows. The Marketplace shows the price for your tier.
Without an active licence
Read only
Previews, audits, recommendations and the log stay available. Review your instance before you buy, and keep your log if a subscription lapses.
FAQ
The read-only audits work even without a licence. Nothing changes until you decide it should.
Admin Ops for Jira