BulkPulse for Jira

Power bulk actions for Jira Cloud: choose issues with JQL, preview every change (dry run), apply it with your own permissions, follow the progress per issue, export the results as CSV and undo field changes for 7 days. By PuzariCloud.

Where to find it

1. Choose issues

Type a JQL query (Ctrl/Cmd+Enter searches) and click Find issues. The list shows 50 issues per page with the total count. Run the action on all matching issues or tick issues on any page and choose Only selected. One bulk change handles up to 1,000 issues.

2. Choose an action

ActionWhat it doesUndo
Add / remove labelsAdds and removes labels in one step; other labels stay.Yes
Add / remove componentsBy name; the component must exist in each issue's project.Yes
Set or clear a fieldText, paragraph, URL, number, date, date-time, select, multi-select, user, multi-user, priority, due date, assignee and labels-type custom fields.Yes
Change fix versionsMove from → to (only issues that have the old version) or add/remove.Yes
Add a commentPlain text with variables (below). In service projects, tick Internal note to hide it from customers.No
TransitionBy transition name or target status. Issues without that transition, or already there, are skipped and listed.No
Link to an issueAny link type, either direction ("blocks" / "is blocked by"). Existing identical links are skipped.No
CloneInto the same or another project, with a summary prefix; choose what to copy; optionally link each clone to its original.No
Watch / unwatchFor you or someone else (needs "Manage watchers" for others).No
DeleteOnly after typing DELETE and the exact number of issues. Issues with sub-tasks are skipped unless you tick Also delete sub-tasks.No

Comment variables

{{key}} {{summary}} {{status}} {{type}} {{priority}} {{assignee}} {{reporter}} {{project}} {{url}} {{date}} (YYYY-MM-DD, UTC) and {{user}} (you). Add a default after a bar: {{reporter|the reporter}}.

3. Dry run, run, results

Undo

For labels, components, fields and fix versions BulkPulse saves each issue's previous value before changing it. Undo this change (on the result or in History) restores them for 7 days. An issue that someone changed again after the bulk edit is left as is and listed as skipped, so undo never overwrites newer work.

Permissions and security

Every read and change is made as you (Jira's asUser), so BulkPulse can only do what your Jira permissions allow, and the history shows you as the author. Background jobs run as the person who started them. Each person only sees their own bulk changes. BulkPulse runs on Atlassian Forge ("Runs on Atlassian") and makes no calls outside Atlassian. See the privacy policy.

Moving from Bulk Action Tools

That Connect app can no longer receive updates and its support ends on 31 January 2027. BulkPulse covers its bulk actions (labels, components, fields, comments, transitions, links, clone, watchers, fix versions, delete) and adds a dry run, background jobs, CSV results and undo. Nothing needs migrating: install BulkPulse, run your usual JQL and pick the action.

Limits

Support

Email support@puzaricloud.in. We reply within two business days.

How to bulk clone issues in Jira Cloud · How to bulk link issues in Jira