Automation Rules now travel with your data – backup, restore, sandbox copy & config promotion

[#1]

Behind every smooth-running Jira Service Management instance, there's a web of automation rules doing some of the heavy lifting – routing requests, updating fields, firing off notifications – so your team never has to think twice about the repetitive stuff. Until now, those rules were difficult to back up, restore, or move between sandbox and production. That's now solved.

Today we're announcing that Automation Rules are now supported across three of the most-requested administrative workflows: Backup & Restore, Sandbox Full Data Copy, and Sandbox Config Promotion (Open Beta). Whether you're recovering from an incident, refreshing a sandbox to test changes, or promoting tested configuration into production, your automation rules now travel with your data.

What's now supported

We've heard from admins that automation rules were one of the biggest gaps in their backup and promotion workflows. You'd spend hours building and fine-tuning rules in a sandbox, only to have to manually recreate them in production – or worse, you'd recover from an incident and realize your automation logic didn't come along for the ride. With this update, your automation rules are treated as first-class configuration: portable, recoverable, and promotable alongside everything else.

Workflow	What this means for admins
Backup & Restore	Project automation rules and global automation rules are now included in your backup & restore flows. If you ever need to restore your instance, your automation logic is preserved.
Sandbox Full Data Copy (FDC)	When you copy production into a sandbox, your automation rules come along, so you can validate behavior with real configuration before making changes.
Sandbox Config Promotion	When you're ready to promote configuration changes from sandbox to production, your automation rules promote with the rest of your config.

This is part of a broader investment in ensuring Jira Service Management and Jira admin workflows are enterprise-grade – predictable promotion, reliable recovery, and configuration you can trust to move cleanly between environments.

Try it now

These capabilities are rolling out across regions now. If you don't see them yet, you will soon. We've updated the Backup & Restore, Sandbox Full Data Copy, and Config Promotion documentation with the full list of supported entities — check those for the latest details.

As always, we'd love to hear how this lands for your team. Drop a comment below if you have questions or feedback.

[Jason Krewson]

This is a great win for JSM, but when is this coming to Jira? 

These automation rules (and app information still) not being stored in our backups or our sandbox refresh was something I always thought was a huge miss, one of those odd things that make ya think, how did they miss this? Or who made that strange decision to exclude this critical data?

Currently I manually back these automation rules up just in case something happens to our site or to the rules. I have Power Automate do the Jira and Confluence backups as well, fully automated this part. So it would be amazing to have this added to Jira.