Exciting update: Revyz is now part of Spin.AI. Read the Press Release here.
Revyz Command Center for Jira
Revyz Command Center for Jira
Breadcrumbs

JSM Operations

About this Page

This page provides step-by-step instructions for configuring, running, and troubleshooting backups for Jira Service Management (JSM) Operations in Revyz. Learn how to enable backup for JSM operations, execute scheduled or on-demand backups, and export raw configuration data.

What is the Use Case?

Protect your Jira Service Management (JSM) Operations setup by backing up critical workflow configurations, including alert policies, routing rules, and escalations, to manage accidental configuration drift or data loss.

This feature is applicable to:

  • Command center for jira standard feature; includes full JSM Operations coverage (configurations + data).

  • CONFIG MANAGER FOR JIRA standard feature; includes JSM Operations configuration backup only.

Prerequisites to enable JSM Operations backup

  • App Version: Ensure Revyz is upgraded to the latest version. Older versions will display an "Update required" notification banner in Backup Settings.

  • Atlassian API Token: User-level API token linked to your Atlassian account. Learn how to add here.

  • Atlassian Admin API Key: Organization-level key generated from Atlassian Organization Settings. Learn how to add here. 

  • Backup settings enabled for JSM Operations

Note: If either token is missing or expired, Revyz will display direct configuration links on the Backup Settings page.

How to backup JSM Operations? 

Supported JSM Operations Configuration Items Once prerequisites mentioned above are fulfilled to enable backup of JSM operations, the automated schedule or manual trigger backs up 12 core configuration items:

  • Alert Policies

  • Integrations

  • Schedules

  • Escalations

  • Maintenance

  • Syncs

  • Global Roles

  • Notification Policies

  • Team Roles

  • Heartbeats

  • Routing Rules

  • Teams

How to Run an On-Demand Backup for JSM Operations?

Step 1: Enable Backup Settings
image-20260807-131049.png
image-20260811-062555.png


Ensure that backups are enabled for JSM Operations Configurations. For enabling, you need to ensure that both Atlassian API Token and Atlassian Admin API Key are enabled. If either or both of them are missing, you will be redirected to the settings to enable them.

Note that invalid or expired tokens may case the backup job to fail.

Step 2: Start backup
image-20260807-125343.png

    • Open the Revyz Command Center for Jira dashboard.

    • Locate the Data Security and Compliance section and click the Backup card.

Step 3: Configure Backup Scope and Snapshot Tag
image-20260807-142909.png

  1. On the On Demand Backup screen, check or uncheck the relevant data options based on your backup needs (e.g., JSM Operations Configuration, Assets Objects, Jira Work Items, or Jira Configurations).

  2. Expanding JSM Operations Configuration displays the included objects: Alert Policies, Escalations, Global Roles, Heartbeats, Integrations, Maintenance, Notification Policies, Routing Rules, Schedules, Syncs, Team Roles, and Teams.

  3. Enter a descriptive label in the Enter tag for backup snapshot text field to easily identify this backup later (e.g., JSM Operations test backup).

Step 4: Execute the Backup Job
image-20260807-143613.png

  • Click the Backup now button at the bottom of the page.

  • When the confirmation dialog appears, click Backup Now to start the process.

Step 5: Monitor and Review Job Status
image-20260807-144052.png


image-20260807-144221.png


  1. Access the job tracker by navigating to Core Administration > Revyz Jobs > Backup Jobs.

  2. Locate your backup run in the job list and click on its Job ID.

  3. Verify the job metadata, including Status (QUEUED, RUNNING, or SUCCESS), Tag, Type, Initiator, Start/End Time, and Time taken.

Step 6: Download Raw Backup Data
image-20260807-144837.png

  • Click the Download raw data button on the job details screen.

  • Select specific configuration items or check Select all.

  • Click Download to export the selected data files.


Troubleshooting

  • Invalid Credential Status: Jobs rely on API tokens and keys as security credentials to authenticate communication with external systems (like Atlassian or administrative endpoints).

  • If a job fails due to an invalid credential error:

    1. Identify the expired key: Check the job logs to see whether the Atlassian API Token or Admin API Key expired.

    2. Update credentials: Go to Backup Settings and save valid tokens.

    3. Retry: Re-trigger the job.


Frequently Asked Questions


Why can’t I see or enable JSM Operations Configuration backups in my settings?

This feature requires a latest version update. If you are on an older version of Revyz, you will see an "Upgrade required" notification banner or prompt in your Backup Settings. Upgrade to the latest Revyz release to unlock this functionality. A toaster message is shared to indicate that update is required to include JSM operations in the backup. 

Which credentials are required to enable JSM Operations backups?

You need two credentials configured under Backup Settings:

  • An Atlassian API Token (associated with your user account).

  • An Atlassian Admin API Key along with your Organization ID (generated from Atlassian Organization Settings).

If either token is missing, direct navigation links will appear in your Backup Settings UI to help you quickly generate and paste them.

What should I do if a backup job fails with an "Invalid Credential" status?

This status occurs when either the Atlassian API Token or the Admin API Key has expired, been revoked, or contains an invalid value. Open the failed job's details and check the logs to see which token caused the issue, update the token under Backup Settings, and re-trigger the backup job.

Can I inspect or download raw backup data for specific JSM Operations items?

Yes. In the Backup Jobs view, filter by JSM Operation Configuration and open the relevant job. You can download raw JSON data for all items combined or download individual configuration files (e.g., specifically downloading Alert Policies to view policy IDs, team assignments, and operational parameters).

Are JSM Operations backups triggered automatically or manually?

Both. Once credentials are set up and the feature is enabled, Revyz includes JSM Operations in your automatically scheduled backup window through the backup settings page. You can also trigger an on-demand backup at any time from the Backup Jira Configurations page.