AN ADD-ON TO REWIND BACKUPS FOR JIRA

Back up ScriptRunner, recover scripts in minutes, keep Jira moving.

Atlassian keeps Jira running. When a scheduled job or script listener disappears, you own the recovery. Resilience starts there: Rewind backs up your scripts, listeners, jobs, and fields, and restores them while keeping what your team added since.
organizations protected worldwide
0 +
of customer data safeguarded
0 PB+
What Rewind backs up

Ten ScriptRunner resource types, backed up daily.

Scripts

Each script and its complete code, restored alone or as part of a suite.

Scheduled jobs

Each scheduled job, restored on its own or with a full configuration restore.

Script listeners

Each script listener, restored by merging in, so anything added since stays put.

Script fragments

Each script fragment, restored by merging in, keeping your team's newer work in place.

Behaviours

Each behaviour, restored on its own or with the rest of your configuration.

Scripted fields

Each scripted field, restored as a live custom field running the same script.

Script variables

Each script variable, restored by merging in alongside the ones your team added since.

Script folders

Your Script Manager folders, restored first, since the scripts inside depend on them.

Escalation service

The escalation service configuration, restored on its own or in full.

Settings

ScriptRunner's own settings, backed up daily and browsable for reference.

Built on Rewind Backups for Jira

ScriptRunner backup and restore is an add-on to Rewind Backups for Jira. Your Jira instance needs an active Rewind Backups for Jira subscription on the Advanced or Enterprise plan before ScriptRunner coverage can turn on.
Why it matters

Your Jira workflows run on ScriptRunner. Protect the logic behind them.

Scheduled jobs and listeners work out of sight.
Scheduled jobs and script listeners do their work in the background. If one disappears, Jira still looks healthy with no error, the automation stops, and the first sign is work piling up downstream. Resilience means catching that before it becomes an incident.
When a script breaks after an edit, the first question is what changed and when. Rewind keeps a version history and diff on the scripts you own, so your team gets a precise answer and moves on.
Script logic that took a team weeks to get right can vanish in one accidental deletion. Rewind keeps versions recoverable, so getting it back is a restore instead of rebuilding it from whoever remembers how it worked.
Resilience

Restore one script, or the whole configuration in order.

Resilience is recovery built into the way your Jira admins already work: a deleted job or a bad script edit becomes a restore instead of rebuilding from memory.
01

Pick the backup from before the loss.

Open your Jira instance in Rewind and choose any backup from before the loss. Your scripts, jobs, listeners, fragments, behaviours, fields, variables, and folders from that point are ready to restore.
02

Restore what you need and keep newer work.

Bring back a script, job, or listener on its own, or your full ScriptRunner backup. Fragments, listeners, and variables restore by merging, so anything your team added after the backup stays exactly where it is.
03

Folders and fields come back in order.

Script folders restore first, since scripts inside Script Manager depend on them. A deleted scripted field comes back as a live custom field again, ready to wire back into the boards and filters that use it.
Use cases

However things go wrong, Rewind helps you recover.

Recover a scheduled job someone deleted

A scheduled job that posts status updates gets removed during cleanup. Restore it from Rewind and the job, its schedule, and its script come back together, ready to run on its next cycle.

Roll back a script after a bad edit

An automation update breaks a script listener in production. Restore the script from a backup taken before the change, and the listener keeps running the version your team trusts, with the rest of Script Manager left as it is.

Bring back a whole ScriptRunner configuration

When a large cleanup goes further than planned, an account-level restore rebuilds scripts, folders, jobs, listeners, fragments, behaviours, fields, and variables in the order they depend on each other, so the rebuilt configuration actually runs.

Compare and copy any past script version

An admin needs a piece of logic from an earlier version of a script. Open any past version in Rewind, see exactly what changed in the diff, and copy the code straight from the vault, skipping the restore step.

Features

The capabilities your team needs to protect ScriptRunner data.

Backup

Recovery

More integrations

Rewind is the SaaS resilience platform behind the tools your Jira admins rely on.

Recover boards, workflows and work items.

Back up and restore QA test data inside Jira.
Confluence

See pricing

Protect the documentation and specs your QA team references daily.

Protect your automation logic. Keep Jira workflows running.

Frequently Asked Questions

What organizations ask before they turn on ScriptRunner backup.

Do I need Rewind Backups for Jira to use this?
Yes. ScriptRunner backup and restore is an add-on to Rewind Backups for Jira, included on the Advanced and Enterprise plans. Turn it on from your existing Rewind account once Jira backup is active; the Rewind Backups for Jira installation you already have is all it needs.
Fragments, listeners, and variables restore by merging, so anything your team added after the backup stays exactly where it is. A script restore replaces that specific script’s content, which is the one you’re choosing to roll back. Everything else in Script Manager stays as it is.
Rewind restores it as a new, live custom field running the same script. Update your boards, filters, and JQL to point at the restored field, and the field and its data are back the way they were before the deletion.