Skip to main content
Skip table of contents

Revert bulk changes in Jira

This is still in BETA, but if you’re interested, please read about the upgrade option

How to upgrade your subscription plan and get "Bulk Revert" option

or reach out to us at

support@saasjet.atlassian.net  for more information.

https://saasjet.atlassian.net/servicedesk/customer/portal/1

In Jira, you can make multiple changes to your issues simultaneously. This operation is called a Bulk Change. For example, you can edit some field values of issues or move issues to a different project.

You need to have relevant permissions. Read about how to make bulk edits and what fields can be bulk edited.

Sometimes, it even happens that Jira automation can make some unwanted changes to your issues. For instance, update descriptions for hundreds of tasks.

However, Jira does not have a built-in option for reverting bulk changes. So, we decided to implement it for Issue History for Jira.

Bulk Revert operation helps you undo previously made incorrect bulk changes after automation or manual actions.

Bulk revert-Final-animation.gif

How does the Bulk Revert feature work?

The Bulk Revert option is available with the Activity View. Follow the next steps to start this process.

  1. Switch to the Activity View and filter issues (select project, dates, updater, etc.)

Issue history filtering.png
  1. You will see checkboxes only for changes supported to bulk revert. Choose changes you want to revert by checking off the boxes.

bulk revert changes.png
  1. Start the Bulk Revert operation.

bulk revert changes jira.png
  1. Review the result.

revert bulk changes.png

What fields are supported for Bulk Revert operation?

Currently, the app supports the Bulk revert for such fields:

Assignee, Reporter, Labels, Summary, Description, Environment, Date, DateTime, User picker fields, Checkbox fields

✅ *Status field - supported; however, if the transition to the status is not possible from the current status (blocked in settings), then there will be an error.

✅ *Priority and Issue type - supported, but if the task was moved from one project to another, it might not be reverted.

✅ *Parent - supported, but it is not possible to take away for subtasks, so the checkbox for such cases will be disabled

✅ *Sprint - it is impossible to revert a closed sprint; only an active or future one.

Not supported fields:

Project, Issuekey, Comment, Worklog, Issuelinks, Created, Creator, Flagged

We'd love your input!
Have any changes in Jira that you'd like to bulk revert? Let us know how we can help improve your experience by filling out the form below. Your feedback will help us better understand your needs!

Submit your request here:

Thank you for helping us make Issue History for Jira even better!

Haven't used this add-on yet, then you’re welcome to try It ⬇

https://marketplace.atlassian.com/apps/1220385/issue-history?hosting=cloud&tab=overview&utm_source=Confluence&utm_medium=refferal&utm_campaign=Documentation_Report-generation-with-Issue-History

 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.