Coming from Jira
Linear uses many familiar ideas, but some of them work differently.
Translate the basics
The mapping is close but never exactly one to one, so treat it as a starting point.
| In Jira | In Linear |
|---|---|
| Initiative or theme | Initiative |
| Program | Sub-initiative or project |
| Epic | Project, with milestones for its phases |
| Sprint | Cycle |
| Story, task, or bug | Issue |
| Sub-task | Sub-issue |
| Component or custom field | Labels |
| Board or filter | View |
What works differently
- Issues do not have types
In Linear, a story, task, or bug is an issue. Use labels when you need to categorize work. - Teams own workflows
Each team defines the statuses it uses. Projects use the workflow of the teams contributing work to them. - Cycles replace sprints
Cycles are repeating planning periods. Teams can schedule them to start and end automatically, and configure how unfinished work carries over. - Views replace boards and filters
Use views to organize and track work in the way that is useful for your team.
Migrating from Jira
If your organization is still transitioning, an admin can either import existing Jira work or set up Jira Sync to keep both tools up to date during the changeover.