How to Bulk Edit Jira Issues (Without Clicking Each One)

If you’ve ever had to update 30 Jira tickets from “In Progress” to “Done,” or reassign everything in a sprint after a team reshuffle, you know the pain of clicking issue by issue. There’s a better way.

Here’s how to use Jira’s native bulk edit feature, when it falls short, and how teams are automating this type of work entirely.

Jira’s Built-In Bulk Edit

Jira Cloud has a bulk edit feature that most users never discover. It works from the issue backlog or board view.

How to access it:

Go to your project backlog (Board view also works)
In the upper right, click the ”…” menu and select “Bulk change all X issues” - or use the keyboard shortcut Z while in the backlog
Select the issues you want to edit (click the checkboxes that appear to the left of each issue, or “Select all”)
Click “Next” to choose your bulk action

What you can do with bulk edit:

Transition issues - move them all to a new status at once
Assign - change the assignee on all selected issues
Move - move issues between projects
Delete - remove multiple issues at once
Edit fields - update priority, fix version, component, labels, story points, and custom fields across all selected issues
Watch/Stop watching - subscribe or unsubscribe from notifications in bulk

The filter approach:

For more targeted bulk edits, use the Jira issue search (Issues - View all issues) with JQL to precisely filter which issues you want to touch:

project = "YOUR-PROJECT" AND status = "In Progress" AND sprint in openSprints() AND updated <= -7d

This returns all in-progress issues from the current sprint that haven’t been updated in over 7 days. Select them all, then bulk-edit to reassign, reprioritize, or transition.

Common Bulk Edit Use Cases

End-of-sprint cleanup: Select all incomplete issues in the current sprint and move them to the next sprint or backlog.

Reassignment: When someone leaves the team, bulk-reassign all their open issues to another team member.

Mass labeling: Add a “needs-review” or “tech-debt” label to a set of issues you’ve identified for grooming.

Priority adjustment: After a product review, bump a batch of issues from Medium to High priority.

Version assignment: Tag a group of issues with a new fix version after a scope decision.

The Limits of Manual Bulk Editing

The built-in bulk edit handles field updates well, but it still requires someone to:

Know which issues need updating
Build the right filter to find them
Decide what changes to make
Actually run the bulk edit

After a sprint planning meeting or a stakeholder review, this process usually falls to the product manager - and it tends to happen a day or two after the meeting, with context already fading.

Automating Bulk Updates After Meetings

The most common reason teams need to bulk-edit Jira is that something happened in a meeting that affected multiple tickets. A scope change. A reprioritization. A decision to deprioritize a whole feature area.

Telos handles this automatically. After your sprint planning, standup, or product review:

Telos cross-references the meeting discussion with your current backlog
It identifies which existing tickets are affected by what was discussed
It proposes a batch of updates - priority changes, status transitions, context additions, new ticket creation - for your review
You approve or reject each proposed action in your Slack channel
Approved actions execute in Jira immediately

The key difference: Telos identifies which tickets need updating based on what was said in the meeting. You don’t have to figure out the filter, you just review the proposed changes.

This is especially valuable for:

Reprioritizing several backlog items after a customer call
Closing or downgrading multiple tickets after a scope cut
Adding meeting context to existing tickets so engineers have the full picture

When to Use Each Approach

Situation	Best Approach
Reassigning issues after a team change	Jira bulk edit
End-of-sprint cleanup	Jira automation rule (auto-move incomplete issues)
Updating priorities after a planning meeting	Telos (reads the meeting, proposes changes)
Adding labels for a new initiative	Jira bulk edit
Capturing what changed after a customer call	Telos (reads context, updates relevant tickets)
Closing stale issues	Jira automation rule (scheduled, inactive issues)

Ready to stop doing bulk Jira updates manually after every meeting? See how Telos works - it handles the updates from standup and sprint planning automatically.