---
title: "Coming from Jira or Linear"
canonical_url: https://zentrik.ai/docs/product/coming-from-jira-or-linear
markdown_url: https://zentrik.ai/docs/product/coming-from-jira-or-linear.md
category: "Product guides"
learning_track: "move-to-zentrik"
last_reviewed: 2026-11-11
---

# Coming from Jira or Linear

Tasks, sub-tasks, cycles and statuses work the way your team expects. Here is what each word becomes, how to bring a team across, and what works differently.



## What each word becomes

| Jira | Linear | Zentrik |
| --- | --- | --- |
| Project | Team | Team, with its own task key |
| Issue, story, task | Issue | Task |
| Sub-task | Sub-issue | Sub-task |
| Epic | Initiative | Initiative |
| Sprint | Cycle | Cycle |
| Status | Workflow state | The team’s status |
| Label, component | Label | Label |
| Fix version | | Label, such as “Release 2.4” |

## Bring a team across, or keep it where it is

| Your team | Runs in Zentrik | Stays in its tool |
| --- | --- | --- |
| On Jira | [Import the project](https://zentrik.ai/docs/product/move-from-jira): issues, sprints, epics and history come across, and Zentrik follows Jira until you switch. | Turn on **Sprints as cycles**: Zentrik shows the sprints and tasks, read-only. |
| On Linear | Keep Linear running for now; a delivery import from Linear isn’t available yet. | Turn on Linear **Cycles**: Zentrik shows each cycle and its issues as they change. |

Either way, an initiative’s stories and tasks go to the tool with **Sync to Jira…** or **Sync to Linear…** on its **Tasks**. See [Zentrik + Jira](https://zentrik.ai/docs/integrations/jira) and [Zentrik + Linear](https://zentrik.ai/docs/integrations/linear).

## What works differently

- **Work carries its why.** A task can sit under an initiative that holds the customer evidence behind it, so the team sees who asked and why it matters.
- **Keys never change.** A task keeps its key, such as LOY-142, when the team changes its key, so links and branch names keep working. Jira re-keys a moved issue; Zentrik doesn’t.
- **Canceled is not done.** Canceled work closes without counting as delivered, and leaves its cycle’s scope and progress.
- **Labels are shared.** One label means the same on an idea, an initiative and a task.
- **Pull requests move tasks.** Start a branch with **Copy branch name** on the task, and its pull request moves the task as the work goes. See [Zentrik + GitHub](https://zentrik.ai/docs/integrations/github#link-task).
- **Work synced from a tool stays in that tool.** Its tasks are read-only here and keep the tool’s keys; change them in Jira or Linear.

## Related guides

- [Move from Jira Product Discovery](https://zentrik.ai/docs/product/move-from-jira-product-discovery)
- [Move from Aha!](https://zentrik.ai/docs/product/move-from-aha)
- [Prepare documents and delivery work](https://zentrik.ai/docs/product/documents-and-delivery)