Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Undoing an unwanted automated bulk edit Edited

I just set up a new JIRA automation, to pre-fill new JIRA ticket description with a template based on ticket type when a ticket is created.

Having created the automation and activated it, I thought I'd try it out, I created a new ticket and then opened it to see no pre-filled description, I then notice my JIRA slack channel has sent me a burst of several hundred messages indicating all existing tickets have been updated, replacing existing descriptions with the template content.

How do I bulk revert these unwanted automated changes, do I have to restore from a backup, assuming I have one?

1 answer

1 accepted

0 votes
Answer accepted

Hi @Jeremy Pitten 

Wow, and sorry to learn that happened.  Luckily the automation rules are limited to 100 issues before they stop execution.  (You disabled that rule, right?)

  • Without any add-ons, you probably want to check for a backup/restore to a test instance, if you regularly backup.  Then you could export and re-import the issues to update the descriptions.  Check with your site admin about backups.
  • If you are coding-savvy, you could use the REST API to get the change logs, parse the JSON, and build something to create an import file.   
  • Otherwise you are back to manually fixing them.

Lessons like this are why I experiment with rules in a test project first, and then copy them into the target project later.

Best regards,


Thanks for getting back to me Bill.

I've been able to fix the issue using the REST API and some javascript; extracting a list of the affected tickets from slack, I was able to fetch the changelog for each ticket, extract the old description and then apply it back, suppressing notifciations.

I havent used this api before so it was useful for me, the documentation is great and api extensive and easy to use.

When I created the automation I didnt disable any rule issue limit, at least not that I'm aware of, I did disable notifications though.

I was using a set of branch rules, each matching on a different ticket type, I didnt realise this would match on all tickets with that type, I thought it would only apply to the ticket I was creating.

I'll take greater care creating these automation rules in future.

Thanks again.

Like Bill Sheboy likes this

Well, done! 

By the way, the issue processing limit of 100 is built into the rule engine (I believe).  When you have branching or triggers using JQL, it can help to test that stand-alone with Advanced Filters to confirm scoping impacts (projects) and issue count limits.


Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,046 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you