Bulk Update Jira Tickets: How to Edit Multiple Issues at Once

There are two reasons teams need to bulk update Jira tickets.

The first is practical housekeeping: you need to reassign a batch of tickets to a new engineer, change the fix version on a set of issues, or move a group of tasks to a different sprint.

The second is more painful: after a planning meeting, a customer escalation, or a strategy shift, your backlog is wrong. Priorities need to change, statuses need updating, and new context needs to be added to a dozen different tickets.

Jira’s native bulk edit handles the first case. The second - which is where the real time sink lives - requires a different approach.

How to Bulk Edit Jira Issues Natively

Jira has built-in bulk edit functionality. Here’s how to use it:

Step 1: Run a search to find the issues

Go to Issues > Search for Issues (or use the board’s filter view). Build a query using the filters or JQL (Jira Query Language) to isolate the tickets you want to update.

Example JQL to find all open issues in a sprint:

project = "Your Project" AND sprint in openSprints() AND status != Done

Or to find issues assigned to a departing team member:

project = "Your Project" AND assignee = "former.engineer@company.com" AND status != Done

Once the search results are displayed:

Click the checkbox at the top to select all results (or select individual tickets)
Click Tools in the top right
Select Bulk Change

Step 3: Choose an operation

Jira’s bulk change tool supports:

Bulk Edit - change field values across multiple issues (assignee, fix version, priority, labels, components, etc.)
Bulk Transition - move issues through a workflow state (e.g., move all selected issues to “In Review”)
Bulk Move - move issues to a different project
Bulk Delete - delete multiple issues at once (use with caution)

Step 4: Apply and confirm

For bulk edit, you’ll see a form showing the fields that can be updated. Fill in the new values, confirm, and Jira updates all selected issues.

Limitations of native bulk edit

The built-in bulk edit is good for structured field changes. What it can’t do:

Add contextual notes or descriptions to tickets (you can’t bulk-write ticket descriptions)
Change priorities based on new information (it changes the field, not the reasoning)
Identify which tickets need updating - you still have to find them first
Update ticket content based on what was discussed in a meeting

The Harder Problem: Keeping the Backlog Current After Every Meeting

The bulk edit workflow described above works when you know exactly what to change. The real challenge is the backlog drift that accumulates over time.

After a sprint planning meeting, the priorities you discussed may differ from what’s in Jira. After a customer escalation call, a handful of tickets should have their severity updated. After an architecture review, some tickets need new context added to their descriptions.

None of this triggers bulk edit. It requires reading what was discussed and knowing which tickets are affected - which is exactly the kind of work that an AI agent handles well.

Telos works like this after every meeting:

Reads the meeting transcript
Identifies which existing Jira tickets are referenced, affected by, or relevant to the discussion
Proposes a set of updates: change priority on these 3, add context to these 5, close these 2 as resolved
The PM reviews the proposed changes in Slack and approves

The result is a backlog that stays accurate after every meeting - not because someone ran a bulk edit, but because the updates were proposed automatically based on what actually happened.

When to Use Each Approach

Situation	Best approach
Reassigning tickets when a team member leaves	Jira native bulk edit
Changing fix version across a release	Jira native bulk edit
Moving tickets to a new sprint	Jira native bulk edit
Updating priorities after a planning meeting	AI-powered autonomous update
Adding context from a customer escalation	AI-powered autonomous update
Closing tickets that were resolved in a standup	AI-powered autonomous update
Grooming stale items from the backlog	AI-powered autonomous update

Think of native bulk edit as the right tool for structured, field-level changes you’ve explicitly decided to make. AI-powered updates handle the continuous, context-driven changes that result from your team’s actual work.

Mass Updating Jira Tickets with JQL + Automation

For teams comfortable with JQL, Jira’s automation rules can trigger bulk updates based on conditions. For example:

When an issue has had no activity for 30 days and is still Open, add a “stale” label
When a sprint is marked Complete, transition all remaining issues to the next sprint
When a linked Epic is marked Done, auto-close all child stories

These automation rules are set up under Project Settings > Automation. They’re useful for systematic, rule-based updates.

The limitation is the same as all rule-based automation: you have to anticipate the condition and define the rule in advance. Changes that require judgment - “this ticket’s priority should go up because of what was said in today’s call” - don’t fit in a rule.

Getting Started

For native bulk edits, Jira’s built-in tools are the right starting point. For keeping the backlog accurate after meetings and calls, Telos handles the continuous update workflow.