Bulker

Perform bulk operations on project roles, users, groups, and all types of schemes. Archive or unarchive multiple projects (spaces) at once, with detailed per-actor logs and a modern UI in one centralized place.

Jira admins spend hours on repetitive role and scheme changes — adding a new team member to 30 projects, swapping notification schemes after a restructure, archiving completed projects at quarter end. Bulker turns those afternoons into 30-second operations, with a clean audit trail of every change.

Update all scheme types in bulk across spaces

Assign and update Workflow, Issue Type, Security, Screen, Field Configuration, Priority, Notification, and Permission Schemes and users in bulk. Change filters & dashboards permissions and ownership.

NEW: Added automation actions!

Use automation with smart values to archive, restore, and add users to your projects!Add users and groups to project roles across multiple projects simultaneouslyArchive and unarchive multiple projects at once

Security & Compliance

Hosted on Atlassian — no external servers involvedData stored within Atlassian — your data stays where your Jira livesDetailed audit logs - showing who changed what and whenData residency compliant

Is Bulker GDPR compliant?

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.

Can I undo a bulk operation if I make a mistake?

Every operation produces an audit log entry with before/after state. For project archiving, unarchive is one click. For role and scheme changes, the audit log shows exactly what changed so you can reverse it manually.

Does Bulker work with Jira Service Management?

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.

How is Bulker different from Jira's native bulk change feature?

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.