CYBBACK| for Jira Cloud
Product Datasheet

Your Jira projects, issues, workflows & configuration - backed up cold.

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.

Issues & commentsAttachmentsWorkflows & schemesAutomation rulesDeleted-issue recycle binEU-hosted
Why CYBBACK

One deletion, one runaway automation rule - and your data is gone

Incremental forever
Only issues changed since the previous run are re-captured (JQL updated ≥ last run). Fast, lightweight backups that respect Jira's API rate limits, full history retained.
Recycle bin for deleted issues
Jira Cloud has no issue recycle bin. CYBBACK detects issues that disappeared between two runs and keeps them, restorable into their original project or any other.
Granular restore
Browse projects and issues, restore a single issue, a whole project or a configuration category - into the original project or another one. Async worker, dry-run available.
Drift detection
Automatic comparison between runs. Get alerted on mass deletions of issues or projects between two backups - before anyone notices in Jira.
AES-256-GCM encryption & BYOB
API token and backup files encrypted at rest. Store backups on your own S3-compatible bucket - your data, your provider, your region.
Readable export
Per-project ZIP with faithful JSON, spreadsheet CSV and an HTML report where every id is resolved to a name (authors, statuses, fields). Usable without Jira.
What gets backed up

Your Jira site, layer by layer

ProjectsKey, name, lead, type, category, components, versions, role actors, associated schemes (company-managed and team-managed)
Issues & subtasksEvery issue type: summary, description, status, priority, assignee, reporter, labels, versions, components, custom fields, story points, time tracking
Comments, worklogs & historyComment threads, work logs and full changelog per issue
AttachmentsFiles attached to issues, downloaded and stored in your bucket
Links, parents & epicsIssue links (same or cross-project), parent/epic links, subtask links
Boards & sprintsScrum and Kanban boards, columns and status mapping, board filters, sprints
Filters & dashboardsSaved filters with their shares, dashboards and gadget configuration
Workflows & schemesWorkflows (statuses, transitions, rules), workflow schemes, screens, screen schemes, issue type schemes, field configurations
Global configurationCustom fields & contexts, issue types, priorities, resolutions, link types, permission / notification / issue security schemes, time tracking
Users, groups & rolesUser directory (for licence counting and name resolution), groups and memberships, project roles
Automation rulesGlobal and project rules via Atlassian's Automation Rule Management API (restored disabled, for review)
Deleted issuesIssues removed from Jira since the previous run are kept in the CYBBACK recycle bin
Technical specifications

Built on the Jira Cloud REST API

AuthenticationDedicated Jira administrator account + Atlassian API token (Basic auth) - encrypted AES-256-GCM in the CYBBACK vault. No Marketplace app, no OAuth consent screen
API endpointsJira 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 modeIncremental forever (catalog/pool). Changed issues via JQL updated ≥ last run (enhanced search, nextPageToken); configuration captured in full on every run
ScopeWhole site or a selection of projects (selector at configuration) · optional categories: attachments, history, worklogs, automation rules, users & groups
FrequencyManual, daily, weekly, or custom cron expression (automatic daily schedule created with the first backup)
Storage backendDefault: CYBBACK secure storage (EU). Optional: BYOB - any S3-compatible provider
Encryption at restAES-256-GCM, optional per-user toggle (JSON .x and binaries .xb). Manifest and browse index excluded from encryption
Restore granularitySingle issue · whole project (with components, versions, boards) · configuration category · group. Subtasks after parents, links after all issues, keys remapped
Restore optionsDry-run · target project (original or any other) · comments · attachments · worklogs · links · history as attachment · recycle bin · asynchronous worker with live logs
Honest limitsRestored 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 exportsZIP 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 detectionOpt-in, 3 severity levels (info / warning / critical). Custom thresholds on deletions of issues and projects
NotificationsIn-app · email · Slack · webhooks
Hosting regionGoogle Cloud - europe-west1 (Belgium)
Trust & compliance

Security you can prove

GDPR-alignedEU residency, DPA on request
AES-256-GCMIndustry-standard encryption
Audit logsEvery action is traceable
EU hostingBelgium (europe-west1)

Start your free trial

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.

Start free trial