Copy a Jira project's schemes onto existing projects (link or clone, with status migration and undo), assign any scheme type, add users to roles, archive projects, rename schemes, manage filters and dashboards in bulk. Previewed and logged.
Jira admins spend hours on repetitive scheme and role changes — making twenty projects look like the one that is set up right, adding a new team member to 30 projects, archiving completed projects at quarter end. Bulker turns those afternoons into one preview and one Apply, with an undo and an audit trail of every change.
Assign any scheme type to many projects, add users and groups to project roles, archive projects, rename schemes and filters to a naming policy, change filter and dashboard owners and sharing — each with a preview.
Pick the project that is set up right and the existing projects that should match. Per scheme type, link the same scheme or clone it for each target. Workflow changes on projects with issues get a status-migration check.
Nothing changes before Apply. Copies can be undone, archives reversed, and every operation is logged with who, when and Jira’s own answer. Runs on Atlassian: your Jira data stays in Atlassian.
Yes. Bulker runs entirely on Atlassian Forge inside your Atlassian Cloud instance. No data ever leaves Atlassian's EU infrastructure, and we don't operate any external servers that process your data.
Yes. The Copy Space Config tab takes the schemes one company-managed project uses — issue type, workflow, screen, field configuration, permission, notification, issue security, priority — and puts them on other existing projects. Per scheme type you choose to link the same scheme or to clone it; a workflow scheme on a project with issues gets a status-migration review before anything is applied.
For Copy Space Config, yes: the last five copies can be undone from the tab — Bulker puts the previous schemes back and deletes the clones it created. Project archiving is reversed with one click. Every other operation produces an audit log entry with before/after state, so you can reverse it from the log.
Yes — Bulker works on any Jira Cloud project type, including Jira Service Management. You can bulk-manage agents, requesters and approval schemes the same way as standard Jira projects.
Jira's native bulk change only operates on issues — it can move issues between projects or change their fields. Bulker operates one level up: on roles, users, groups, permission/notification/issue-type schemes, and projects themselves. These are admin-level operations that Jira has no UI for at scale.