Enterprise-grade, automated backup & recovery for Jira Cloud - projects, issues and subtasks, comments, worklogs, history, attachments, boards and sprints, filters and dashboards, workflows, screens, fields and schemes, groups and roles, automation rules. Incremental, encrypted, restorable issue by issue, with a recycle bin for deleted issues.
updated ≥ last run). Fast, lightweight backups that respect Jira's API rate limits, full history retained.| Authentication | Dedicated Jira administrator account + Atlassian API token (Basic auth) - encrypted AES-256-GCM in the CYBBACK vault. No Marketplace app, no OAuth consent screen |
|---|---|
| API endpoints | Jira Cloud REST API v3 (/rest/api/3), Jira Software Agile API (/rest/agile/1.0), Automation Rule Management API · rate-limit aware (429 + Retry-After, token bucket, back-off with jitter) |
| Backup mode | Incremental forever (catalog/pool). Changed issues via JQL updated ≥ last run (enhanced search, nextPageToken); configuration captured in full on every run |
| Scope | Whole site or a selection of projects (selector at configuration) · optional categories: attachments, history, worklogs, automation rules, users & groups |
| Frequency | Manual, daily, weekly, or custom cron expression (automatic daily schedule created with the first backup) |
| Storage backend | Default: CYBBACK secure storage (EU). Optional: BYOB - any S3-compatible provider |
| Encryption at rest | AES-256-GCM, optional per-user toggle (JSON .x and binaries .xb). Manifest and browse index excluded from encryption |
| Restore granularity | Single issue · whole project (with components, versions, boards) · configuration category · group. Subtasks after parents, links after all issues, keys remapped |
| Restore options | Dry-run · target project (original or any other) · comments · attachments · worklogs · links · history as attachment · recycle bin · asynchronous worker with live logs |
| Honest limits | Restored issues get a new key (the old one is prefixed in the summary). Comment author and date = the restore account and restore time (original author/date annotated inline). 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 |
| Native exports | ZIP per project: issues.json (faithful), issues.csv (spreadsheet), issues.html (readable, ids resolved), attachments in their original format + config/, users, groups, filters, dashboards, automation, HTML summary report |
| Drift detection | Opt-in, 3 severity levels (info / warning / critical). Custom thresholds on deletions of issues and projects |
| Notifications | In-app · email · Slack · webhooks |
| Hosting region | Google Cloud - europe-west1 (Belgium) |
Create a backup account in Jira, generate an Atlassian API token, paste it into CYBBACK - and back up your entire site in under 5 minutes.