Admin Toolkit for Jira
Find any configuration by name or ID and change many projects at once.
Get it on the Atlassian Marketplace →
Overview
Everyday shortcuts for Jira administrators: find any configuration item by name or ID, and apply the same change to components, versions and project roles in many projects at once.
Getting started
- A Jira administrator installs the app from its Atlassian Marketplace listing.
- Open Jira settings (⚙) → Apps and select Admin Toolkit in the sidebar. The page is only available to Jira administrators.
- You can also open Jira's command palette and run Search Jira configuration (Admin Toolkit).
Configuration search
In the Configuration search tab, type at least two characters of a name or an ID and select Search. The results show the type, the name with a link to its administration page, and the ID.
- Projects, custom fields, issue types, statuses, priorities and resolutions.
- Screens, workflows and filters.
Bulk project changes
- In the Bulk changes tab, pick the Projects.
- Choose What: Components, Versions or Project role members, and the Action.
- Fill in the fields for that action (below).
- Select Apply to N project(s). Each project is processed separately, with a progress bar and a result per project.
| What | Actions |
|---|---|
| Components | Create (name, optional description) · Rename · Delete, optionally moving its issues to another component. |
| Versions | Create (name, optional description and release date) · Rename · Merge into another version · Release (with a release date, today if empty) · Archive. |
| Project role members | Add people · Remove people, for the project role you choose. |
Names are matched without regard to case. A skipped result means there was nothing to do in that project, for example the component already exists or the version was not found. A failed result shows Jira's reason.
Merging versions moves the issues of a version to the target version and deletes the merged version. Deleting a component without a target removes it from its issues.
Moving from Admin Toolbox for Jira
Admin Toolbox for Jira is an app for Data Center. Atlassian Data Center reaches end of life on 28 March 2029, so if you are moving to the cloud, this app covers the same needs in Jira Cloud.
Nothing needs to be migrated: this app stores nothing.
| If you used | Use in this app |
|---|---|
| The administration quick search | Configuration search, or Search Jira configuration (Admin Toolkit) in Jira's command palette |
| Changes to components, versions and project roles in many projects | Bulk changes |
If you use the Jira Cloud Migration Assistant, you can choose this app as the cloud alternative to Admin Toolbox for Jira when you assess your apps.
Limitations
- Everything runs with your own administrator permissions; Jira checks every change.
- The project picker lists up to 1,000 projects; the search shows up to 200 results.
Permissions
| Scope | Why |
|---|---|
read:jira-work | Search projects, fields, issue types, statuses, priorities, resolutions and filters. |
manage:jira-project | Create and change versions and components, and manage project role members. |
manage:jira-configuration | Search screens and workflows. |
Data and privacy
The app stores nothing. Account IDs are only used in the request that adds or removes people from a role. No data leaves Atlassian. See the privacy policy.
Troubleshooting
A change failed in some projects
The result shows Jira's message. Common causes are missing permissions in that project or a name that Jira does not accept.
The app says it needs an active license
The app is paid and checks the license on every request. Ask your site administrator to check the app's subscription in the administration of Jira or Confluence (Apps → Manage apps). During a free trial the app works normally.
Need help?
See the support page.