Linear
BackupLatte is preparing to launch. Account creation and backups are not available yet. Join the waitlist for updates.
What a backup contains
Every backup is a full snapshot of the workspace: 55 sets of Linear data plus copies of the files uploaded to Linear that the data links to, and 5 administration sets more with extended coverage. Archived records are included — they are often the first thing to vanish from a workspace. The Download… panel of each backup lists what it holds, set by set.
Sets of data
"Restored" means a restore can write the set back into Linear. Sets that cannot be restored stay in the download. "Depends on the Linear plan" marks features only some Linear plans have; on a plan without them the set is marked Not on plan and does not count as a gap.
Issues and comments
| Set | Restored | Depends on the Linear plan |
|---|---|---|
| Issues | Yes | — |
| Comments | Yes | — |
| Issue relations | Yes | — |
| Labels | Yes | — |
| Attachments | Yes | — |
| Issue history | No | — |
Projects, initiatives and roadmaps
| Set | Restored | Depends on the Linear plan |
|---|---|---|
| Projects | Yes | — |
| Project statuses | Yes | — |
| Project labels | Yes | — |
| Project dependencies | Yes | — |
| Initiatives | Yes | Yes |
| Initiative updates | Yes | Yes |
| Sub-initiatives | Yes | Yes |
| Initiative projects | Yes | Yes |
| Initiative labels | Yes | Yes |
| Project milestones | Yes | — |
| Project updates | Yes | — |
| Roadmaps (legacy) | Yes | Yes |
| Roadmap projects (legacy) | Yes | Yes |
| Project history | No | — |
| Initiative history | No | Yes |
| Project links | Yes | — |
| Initiative links | Yes | Yes |
Documents
| Set | Restored | Depends on the Linear plan |
|---|---|---|
| Documents | Yes | — |
| Document versions | No | — |
Teams, cycles and workspace
| Set | Restored | Depends on the Linear plan |
|---|---|---|
| Cycles | Yes | — |
| Teams | Yes | — |
| Workflow states | Yes | — |
| Team memberships | Yes | — |
| Users | No | — |
| Shared views | Yes | — |
| Custom emojis | Yes | — |
| Templates | Yes | — |
| Schedules | Yes | Yes |
| Triage responsibilities | Yes | Yes |
| Cycle links | Yes | — |
| Git automation | Yes | — |
| Team posts | No | — |
| Team pinned resources | No | — |
| Team resource sections | No | — |
| SLA configurations | No | Yes |
Releases
| Set | Restored | Depends on the Linear plan |
|---|---|---|
| Releases | Yes | Yes |
| Release pipelines | Yes | Yes |
| Release stages | Yes | Yes |
| Release notes | Yes | Yes |
| Issues in releases | Yes | Yes |
| Release history | No | Yes |
| Release links | Yes | Yes |
Customers
| Set | Restored | Depends on the Linear plan |
|---|---|---|
| Customers | Yes | Yes |
| Customer requests | Yes | Yes |
| Customer statuses | Yes | Yes |
| Customer tiers | Yes | Yes |
Agents
| Set | Restored | Depends on the Linear plan |
|---|---|---|
| Agent sessions | No | Yes |
| Agent activities | No | Yes |
| Shared agent skills | No | Yes |
Administration (extended coverage)
| Set | Restored | Depends on the Linear plan |
|---|---|---|
| Workspace settings | Yes | — |
| Audit log | No | Yes |
| Invitations | No | — |
| Integrations (without credentials) | No | — |
| Webhooks (without URLs and secrets) | No | — |
Only shared views and shared agent skills are backed up; private views and personal skills stay personal. Integrations and webhooks are backed up without their credentials, URLs and secrets.
Files
Images and files hosted by Linear (uploads.linear.app and public.linear.app) that issues, comments, documents and other content link to are copied into BackupLatte's storage. Each file is stored once per workspace and shared by every snapshot that links to it, so a daily backup of the same workspace does not store the same file again. The Files set is the index that maps each link to its stored copy; a restore uses it to upload the files again (see Restore).
A file that no longer exists in Linear, or that cannot be copied, is listed in the snapshot as a gap; the rest of the backup is not affected. Files are not copied while your storage is full — see Storage.
Not included
- Authentication, SSO/SCIM, IP restriction and team security settings.
- Personal data of each user: inbox, favorites, drafts and private views.
- OAuth credentials and the secrets of integrations and webhooks.
- Anything the connected Linear user cannot see, such as private teams they are not a member of. See which account to connect with.
States of a set
Each set in a snapshot has one of these states, shown in the Download… panel:
| State | Meaning |
|---|---|
| Complete | Every record was read and verified. An empty set is truly empty. |
| Partial | Stored, but with recorded gaps (the reason is shown). |
| Missing | Could not be collected — no access, or an error from Linear (the reason is shown). |
| Not on plan | The workspace's Linear plan does not have the feature. |
A backup is Success when every set is complete or not on the plan, and Partial otherwise. Without extended coverage the administration sets are not part of the backup at all; the manifest lists them as not covered. With extended coverage but without Linear admin access, they are Missing and the backup is partial. A partial backup can still be downloaded, and every complete set in it can be restored.
History
Issue, project, initiative and release history and document versions only grow when their record changes. For records unchanged since the previous snapshot, the history is carried over from it into the new snapshot; it is read in full again periodically. Each snapshot still holds the whole history on its own.
The manifest
Every snapshot has a manifest.json: for each set its state, record count, size and SHA-256 checksum, plus when the collection started and ended, which Linear user it ran as and with which access. Download it from the Download… panel with Download manifest.json; it is also inside the ZIP. See Snapshots and downloads.
Something missing or unclear? Write to [email protected].