Revyz Command Center for Jira

Export Data (Offline Access)

About this Page

The Offline Access feature is a business continuity solution engineered for mission-critical resilience. While standard backups protect against data loss, Offline Access protects against platform loss. It is designed as a final fail-safe for "black swan" events, such as global outages of major cloud providers, or as a transitionary tool during large-scale platform migrations.

Supported Solutions

This capability is integrated into the following enterprise-tier solutions:

  • Command Center for Jira Advanced (BYOS)

  • Command Center for Confluence Advanced (BYOS)

Core Requirement: Data Sovereignty

To enable Offline Access, your environment must be configured for Bring Your Own Storage (BYOS). By utilizing your own AWS S3 or Azure Blob Storage, your organization maintains absolute custody of the exported data. This feature is not available for Revyz-managed storage.

image-20260324-011514.png

How to Export Data for Offline Access

Use this feature to manually trigger an export of your Jira data into a human-readable format stored within your custom storage.

Navigate to export data
image-20260324-050053.png

In the Revyz dashboard, follow this breadcrumb path: Revyz Command Center for Jira > Data Security and Compliance > Export Data.


Review Exported Items
image-20260324-050214.png


Before initiating, see the types of data included in the export. By default, the system will export:

  • Work Items (Issues)

  • Comments

  • Worklogs

  • Attachments

  • Links

  • Votes

Tag Your Export Job

Locate the text field labeled "Enter a tag for export job." > Tip: Use a descriptive tag (e.g., Monthly_Audit_March2026) to help you easily identify and filter this specific export in your logs later.

Initiate Export

Click the Export button at the bottom of the card. Once you click export, a manual job is queued. The data will be processed and transferred to your designated storage for offline access. You can monitor the progress of this job within the Revyz Jobs.

Export Jobs
image-20260324-053729.png

Navigate to: Core Administration > Revyz Jobs > Export Jobs. In this table, you can see a history of all manual exports. Key columns to watch include:

  • Status: Look for a green SUCCESS label. If it shows "Failed," check the Logs tab for specific error details.

  • Time Taken: Displays the duration of the export (typically around 1 minute for standard sets).

  • Download CSV: Use the button at the top right if you need a spreadsheet summary of all export job metadata.

View Detailed Job Results
image-20260324-053957.png

Click on any Job ID (e.g., 25156) to open the specific job details page. This view provides:

  • Initiator: Identifies which team member started the job.

  • Execution Times: Precise Start and End times in UTC.

Access Your Exported Data

Once a job is successful, look at the "What Next?" section at the bottom of the screen:

  • Storage Path: The system provides the exact folder path where your data is stored in your custom storage (e.g., /export-jira/2026-03-17/13:42:32/).

  • Offline Access: Click the "Discover offline access" link to learn how to view this data locally during a Jira outage.

  • Synchronization: For true business continuity, click "Learn how to synchronize" to set up a process that mirrors this cloud storage to your local infrastructure.

Key Use Cases & Strategic Value

True Platform Independence

Unlike traditional Disaster Recovery (DR) which often requires a functioning cloud environment to restore services, Offline Access creates a version of your data that is 100% decoupled from Atlassian, Revyz, and external cloud application layers.

Regulatory & Compliance Readiness

For industries with stringent "Always-On" requirements (such as Finance, Healthcare, or Government), Offline Access provides documented proof that mission-critical intellectual property remains accessible even during a total internet or service provider blackout.

Air-Gapped Business Continuity

The system generates snapshots in a universal, human-readable format. These assets can be localized and viewed without an active internet connection or a live Jira/Confluence instance. This ensures that your team can continue to reference:

  • Standard Operating Procedures (SOPs)

  • Critical Incident Response Documentation

  • Project Historical Records and Attachments

Archival & Migration Support

For organizations transitioning away from Atlassian platforms, Offline Access serves as a high-fidelity, read-only archive.