Tools › Article

Linear for Designers: Issues, Projects, and Cycles Without Losing the Design

How designers can use Linear: issues, cycles, and projects, the Figma integration, and the plans its official page lists, with the limits of each feature.

info Quick Definition
Linear is a work-management tool for product teams. It organizes issues, cycles, and projects, and in design it helps you log requests, plan work in time periods, and connect screens with the tasks developers carry out.

What is Linear, and where does it fit in design work?

Linear is an issue tool: tasks with a status, an owner, and a priority. Its documentation organizes work into three pieces: issues, which are the units of work; cycles, which are time periods per team; and projects, which group issues around an outcome or a target date.

For design, the value is not in the tool itself but in the place where the work crosses over. A Figma screen that becomes an issue, with a status and an owner, stops being a chat conversation and becomes something the team can prioritize.

Why does this matter for a junior designer?

Because in most product teams, design reaches development through a task manager. If you do not know how to log a request, how to mark a design as ready, or how to plan a cycle, you lose track of when what you designed gets built. A junior who knows these pieces becomes more useful to the development team.

The tool also teaches an important distinction: not everything to be done is a project. A cycle measures time and a project measures an outcome, and mixing them up shows on the board.

How do cycles work?

According to Linear’s documentation, a cycle is a period of one to eight weeks, configured per team. These are its main rules:

  • Open issues generally roll over automatically to the next cycle when the current one closes. They are not lost, but they stay in the plan.
  • There is an optional cooldown between cycles. Issues cannot be assigned to the cooldown, and issues moved to backlog, triage, canceled, or completed during it do not carry over to the next cycle.
  • Up to fifteen future cycles can be scheduled.
  • Sub-teams inherit the calendar of the parent team.

The practical consequence is that a cycle does not work as a catch-all. If you put everything pending into the current cycle, the rollover will be constant.

What are projects, and how are they used?

According to the documentation, a project is a group of issues with a clear outcome or a planned completion date, and it can span several teams. An issue can only be in one project at a time; to split work across several, Linear suggests creating sub-issues and assigning each to a different project. Each project has a lead, a status, milestones with target dates, and a progress graph.

For design, a project can be a flow redesign, a research effort, or the launch of a feature. A milestone can be “prototype validated” or “design ready for development”. That helps separate discovery work from delivery work, which often get mixed.

How does it connect to Figma?

Linear has a Figma plugin that links frames, sections, or pages to issues, lets you create issues from the canvas, and change status, owner, or project from Figma. Pasting a Figma link into an issue shows a preview, but Linear keeps a snapshot of that moment: even if the file changes, the snapshot stays as it was, and you update it with the refresh button. In addition, whoever installed the integration must have access to the file, or a permissions error (“Insufficient permissions”) appears.

These details matter day to day. If the preview shows an older version, a developer may build on something that has already changed.

What plans does it offer?

According to the pricing page, checked on November 12, 2026, Linear has four plans. All of them have unlimited members, and issues, projects, cycles, and initiatives.

  • Free: 0 USD. Two teams, up to 250 issues, and files up to 10 MB. No guests.
  • Basic: 10 USD per user per month, billed yearly. Up to five teams, unlimited issues and file uploads, and admin roles. No guests.
  • Business: 16 USD per user per month, billed yearly. Unlimited teams, private teams and guests, issue SLAs, and Linear Insights.
  • Enterprise: price on request, annual billing. Adds SAML and SCIM, audit log, HIPAA, and priority support.

The page shows no monthly prices and plans change over time, so confirm before budgeting. If you need guests, for example clients or outside collaborators, you need the Business or Enterprise plan.

When is Linear NOT the right choice?

  • If the design team works alone and no development team follows the board. The cost of maintaining cycles and projects outweighs the benefit.
  • If design work is mostly exploration without dates. A task board with cycles forces planning that exploration does not support. This is a practice criterion, not something Linear states.
  • If you need guests on the free or Basic plan. Only Business and Enterprise include them.

If your team needs open space to think, FigJam or Miro fit better than a task manager. And if the board must live in a more corporate environment, the alternative is Jira, which has its own logic.

Example

Illustrative example: a design and development team of four people works on a payments flow.

  • Project: “Frictionless payments”, with the milestone “prototype validated” and the milestone “design ready for development”.
  • Issues: each screen is an issue, with its Figma frame linked through the plugin.
  • Cycle: two weeks. When the cycle closes, open issues roll over, and the team reviews why they carried over.
  • Problem found: one screen’s preview showed the previous week’s version. Development built on it. The team adds a manual refresh step before marking the issue as ready.

The tool does not prevent the mistake. What it does is make the mistake visible, so it can be fixed within the same flow.

For the AI side of this tool, the article on Linear with agents covers the integration with MCP servers, which is a different topic.

Common mistakes

  • Confusing a cycle with a project.
  • Putting everything pending into the current cycle and not reviewing the rollovers.
  • Trusting the Figma preview without refreshing it.
  • Creating an issue for every small change, which saturates the board.
  • Forgetting that an issue can belong to only one project.
  • Budgeting without checking which plan includes guests.

Sources

Frequently asked questions

What is Linear and what is it for a designer?
It is a work-management tool built around issues, cycles, and projects. For design, it is useful to log requests, plan work in time periods, and link Figma screens to the tasks developers carry out.
What is a cycle in Linear?
A time period set per team, from one to eight weeks according to the documentation. Open issues generally roll over automatically to the next cycle, and there is an optional cooldown between cycles.
What is the difference between a cycle and a project?
A cycle is a time period for doing work, and it is not tied to a release. A project groups issues that have a clear outcome or a planned completion date. One measures time and the other measures an outcome.
How does Linear connect to Figma?
Through a plugin that links Figma frames, sections, or pages to issues, and lets you create issues from the canvas. Pasting a Figma link into an issue shows a preview that is a snapshot of that moment, not a live file.
What plans does Linear offer?
According to its pricing page, checked on November 12, 2026, there is a free plan with two teams and 250 issues, a Basic plan at 10 USD per user per month and a Business plan at 16 USD, both billed yearly, plus Enterprise on request.