Bulk edit, move and delete Jira issues with JQL, safely

The risk in a bulk change is not the change. It is acting on a different set of issues than the one you checked.

The problem

A query like updated < startOfDay() matches different issues a minute later. Native bulk edits also leave you to work out which issues failed and why.

Step by step

  1. Bulk operations. Enter the JQL and preview. Read the match count and the sample of issue keys.
  2. Choose the operation: add label, set a field, transition, move or delete, and confirm.
  3. Read the per-issue result. A partial result across mixed projects is normal; the reasons come from Jira.

What to watch out for

The run acts on the issues the preview resolved, not on a re-run of the query. For delete or move, a match larger than 1,000 is refused outright rather than acted on in part: narrow the query by project, date or issue type until it fits.

Start by seeing what your instance is carrying around

The read-only audits work even without a licence. Nothing changes until you decide it should.