CYBBACK|for Jira Cloud
Quick User Guide

Your first Jira backup
in under 10 minutes.

From sign-up to a fully encrypted, restorable snapshot of your Jira Cloud site - projects, issues, comments, worklogs, history, attachments, boards, filters, dashboards, workflows, configuration and automation rules. This guide walks you through every step.

AudienceJira admins & IT leads
Reading time~ 8 minutes
Setup time~ 10 minutes
VersionEN - 2026
What you'll learn

6 steps to a production-ready backup

1
Get started

Sign up - trial or paid licence

CYBBACK offers two ways to get started. Both unlock the full Jira feature set.

Option A - Free trial

  1. Open cybback.com/essai-gratuit.
  2. Fill in your work email, company and a password. Click Start free trial.
  3. Confirm via the verification email.
  4. Your trial workspace is provisioned instantly - every application, Jira included, is available during the trial.
Painless onboarding

Trial accounts get the full Jira feature set - AES-256 encryption, BYOB, scheduling, granular restore, recycle bin. Switch to a paid plan at any moment without losing data.

Option B - Paid licence (Stripe checkout)

  1. Go to cybback.com/tarifs and pick the tier that matches your storage needs. CYBBACK is priced per protected user: a Jira user is a billable Atlassian account (bots and deactivated accounts are never counted).
  2. Click Subscribe. Stripe Checkout supports cards, SEPA and invoicing on annual plans.
  3. Your licence is active immediately - visible under Account → Subscription.
2
Connect Jira

Create the backup account & API token

CYBBACK talks to Jira through the Jira Cloud REST API, authenticated with an Atlassian API token issued to a dedicated backup account. No Marketplace app to install, no OAuth consent screen.

Create a dedicated backup account (recommended)

  1. In admin.atlassian.com, invite a user such as backup@yourcompany.com to your Jira site.
  2. Give it the Jira Administrator product role (global configuration, schemes, workflows, fields, project creation) - and Organization admin if you want groups and their members backed up.
  3. Grant access through a dedicated group (e.g. svc-backup) containing the account, never project by project: give the group the global permissions Browse users and groups and Share dashboards and filters, then add it to the permission scheme used by the projects to protect (a shared copy of the default scheme works well) with Browse Projects, View Voters and Watchers, View All Worklogs, and for restore Administer Projects, Create / Edit / Assign / Resolve / Link Issues, Assignable User, Modify Reporter, Schedule Issues, Add Comments, Create Attachments, Manage Watchers, Work on Issues. A replacement account only has to join the group. Team-managed projects: add the group to the project’s Administrator role.
  4. Share with the group the dashboards to protect (Jira only exposes dashboards shared with the account).
  5. Service account language: keep it in English (en-US) and do not change it.
  6. Service projects (Jira Service Management): give the account access to the Jira Service Management app (admin.atlassian.com → account → app access). Without it, Jira treats it as a portal customer and hides the requests. Also add the group to the Service Desk Team role of each service project: without it, request type, participants, SLAs and approvals are refused.
Why a dedicated account?

An API token sees exactly what its owner sees and dies with its owner's account. A dedicated account survives staff changes, keeps restore actions clearly attributed ("restored by backup@…"), and lets you scope its permissions precisely.

Generate the API token

  1. Signed in as the backup account, open id.atlassian.com → Security → API tokens.
  2. Click Create API token, give it a label (e.g. CYBBACK) and copy the value - it is shown only once.
  3. Prefer a classic token (no expiry). If you use a scoped token, grant the read and write scopes listed in CYBBACK's configuration guide so the restore works too.

Connect the site in CYBBACK

  1. Open app.cybback.com/dashboard/jira-backup → Configuration.
  2. Enter your site URL (https://yourcompany.atlassian.net), the backup account email and the API token, then click Validate. CYBBACK calls GET /rest/api/3/serverInfo, GET /rest/api/3/myself and lists your projects to confirm the access and the permissions.
  3. The token is encrypted (AES-256-GCM) and stored in the CYBBACK vault. It is never shown in clear again.
Revoke and rotate the token

A classic Atlassian API token stays valid until revoked. If it leaks, revoke it from id.atlassian.com → API tokens and update the credential in CYBBACK's Configuration. CYBBACK flags a revoked token immediately (no silent retries).

app.cybback.com/dashboard/jira-backup
Dashboard
Configuration
Jira Cloud connectionEncrypted at rest

Site URL, backup account email and Atlassian API token.

 ✓ CYBBACK Backup - Jira admin · 12 projects · 25 billable users
3
Backup scope

Pick what to back up

After validation, choose the projects to protect and the optional data categories. The scope can be changed at any time without re-entering the token.

Projects

What is captured on every backup

Optional categories (toggles)

Dashboard → Jira → Configuration
Backup scopeSite: acme.atlassian.net
PLAT - Platform6,120 issues
SUP - Customer support9,840 issues
SBX - Sandbox210 issues
AttachmentsFiles attached to issues
History & worklogsChangelog and work logs per issue
Automation rulesGlobal and project rules
Incremental forever

After the first full backup, CYBBACK only fetches issues changed since the previous run (JQL updated ≥ last run, enhanced search). Configuration objects are small and captured in full every time. A daily backup of a large site transfers virtually only the delta - and stays well within Jira's API rate limits.

4
Bring Your Own Bucket

Use your own S3-compatible storage

Want full data sovereignty? Point CYBBACK at your S3-compatible bucket - AWS S3, GCS, Scaleway, OVH, Wasabi, MinIO. Your data, your provider, your region.

Provision the bucket

  1. In your S3 provider, create a private bucket (no public access, versioning recommended).
  2. Create an access key / secret key with permissions limited to that bucket.
  3. Note your endpoint URL and region.

Configure CYBBACK

  1. Open Dashboard → Storage.
  2. Select My own S3 storage.
  3. Fill the form, click Test connection, then Save.
Dashboard → Storage
S3 ConfigurationEncrypted at rest
 
5
First backup

Run your first backup

You're now fully configured. Time to run your first Jira snapshot - manually for instant peace of mind; a daily schedule is created automatically with it.

Manual backup

  1. Go back to the Dashboard tab.
  2. Click Run backup now. The job appears with status pending, then running, with a progress bar and the current phase (site, users & groups, configuration, projects, issues, attachments, boards, filters & dashboards, automation).
  3. Once finished, the history line shows the counts (projects, issues, comments, attachments) and the size really stored by this run. Partial failures are listed unit by unit under the line.

Automatic daily schedule

  1. The first backup creates a schedule Auto - Jira (daily at 03:00 Europe/Paris) - a toast confirms it, and the dashboard shows the next run.
  2. Change the frequency from Dashboard → Schedules: Daily / Weekly / Custom (cron).

Track your backups

Jira rate limits

Jira Cloud applies cost-based and burst rate limits per site and answers 429 when exceeded. CYBBACK applies an internal token bucket, honours Retry-After and backs off automatically - so a very large site simply takes a little longer on its first full run, without ever failing on a 429.

6
Restore

Restore - issue, project, configuration

CYBBACK restores from any previous snapshot. Recreate a single issue, a whole project with its issues, a configuration category, or recover a deleted issue from the recycle bin - into the original project or a different one.

The 3-step restore flow

  1. Selection. Open the snapshot, browse the projects, search issues by key or summary, preview any issue (JSON + attachments) and tick what you want to recover. Toggle Recycle bin to see issues deleted from Jira since the backup.
  2. Options. Choose your safety net:
    • Dry-run - simulate, no write to the Jira API. The worker lists what it would create.
    • Target project - leave empty to restore into the original project (recreated if missing), or pick another existing project.
    • Comments, attachments, worklogs, links, history - each can be included or skipped.
  3. Execution. The async worker recreates the project (components, versions, roles), then issues (parents before subtasks), comments, attachments, worklogs and finally issue links. Live logs and counters are shown on the page; a summary lists what was created, skipped or failed.
Dashboard → Jira → Restore
1. Selection
2. Options
3. Execution
Choose itemsSnapshot from Nov 10, 2026
Project - SUP Customer support9,840 issues
SUP-4120 - Login fails after SSO rolloutdeleted · recycle bin
SUP-4098 - Invoice PDF missing attachments3 attachments
SUP-4001 - Onboarding checklist2 subtasks
Configuration - Custom fields42 fields

Best practices

Honest restore limits

The Jira API recreates objects under the backup account: restored comments and worklogs carry that account as author, with the original author and date annotated inline. Issue keys and ids change. Workflows (statuses and transitions - transition rules such as conditions, validators and post-functions are not rebuilt), screens, screen schemes, field configurations and their schemes, and workflow schemes are recreated under their own name when missing on the target; they are not assigned to an existing project automatically; sprints are captured on issues but not recreated; automation rules are recreated disabled for review. Restore faithfully rebuilds projects, issues and their content, but it is not a bit-for-bit revert of the site.

You're all set.

Need help? Our team replies within one business day on every plan.

Contact support →