What should you put in your first Linear issue?

An issue is one record of work. Give it a title and status in the right team, assign one person, and write a check that tells them when the result is ready.

Record the problem you can observe
On paper, name a fake issue “Booking stays on Saving after a failed request.” Add the steps that trigger a known rejection before anything is saved, and write the message you expect to see.
Set one owner and one test condition
Name the person who will check the result. Add what should happen when a fake booking succeeds, so the fix does not make the working path worse. Keep real customer details, bookings and credentials out of the rehearsal.
Keep the reason near the work
Note the decision that matters, such as keeping the chosen time when a request fails. Put a longer decision in a document and link it from the issue so it has one home.

How do you connect an issue to a GitHub pull request?

Start by adding the pull request link to the issue. Once GitHub is connected, Linear can also recognize the issue ID in the branch name or pull request title. A pull request is the proposed code change that a teammate can review.

A GitHub organization owner can authorize organization access, or a repository administrator can install at repository scope. Check what the connected pull request can display. Linear linkbacks can include an issue’s title and description. For private team issues, Linear documents a narrower ID-and-link notice.

Choose what the connection should do
If you want to	How it works
Associate a pull request without changing issue status	With the integration set up, use “Relates to” and the issue ID in the pull request description. A closing phrase such as “Fixes” can also trigger the team’s configured merge status.
Read and review changes in Linear	Enable code access for the selected repository, connect your personal GitHub account and enable Reviews. Linking a pull request by itself does not require this wider code access.
Approve or merge the change	Use the GitHub review and merge rules for that repository. Check who can approve and which checks must pass. A note on the Linear issue does not satisfy GitHub’s required review.

When is an issue ready to close?

Use the issue status to show what still needs to happen. Keep a merged issue waiting for release until the owner confirms which version reached the intended audience.

A team can set Linear to change status on review or merge events. The Releases feature on Business and Enterprise can use a reported release instead. For the fake booking issue, record the checked version and the outcome in a test copy with separate data and no real messages or charges. Record the release containing that version and confirm what reached the customer address using a read-only check before closing.

You can delegate work to an agent and keep the human assignee responsible. Linear Agent uses the access of the person who invokes it. A separately installed agent needs permission for the team and for the actions it will take. Review the actual code and test evidence before using its result.

What does a Linear export let you keep?

An issue CSV gives you the task fields, such as title, description, status and assignee. Keep the discussion and attachment files you need through separate copies.

Try moving one item first. Open the result outside Linear and see whether the owner, status, discussion and files still make sense. Give the new owner access in the destination before switching the team.

Pick an export or recovery path
What you need	What to use
A list of issues for a move	Export the issue view as CSV. Members can export up to 250 issues at a time. Admins, or Owners on Enterprise, can export views with up to 2,000. A workspace-wide export is separate and requires a workspace admin, or a workspace Owner on Enterprise. Guests cannot export issues.
The context behind one issue	Copy the issue as Markdown to include its comments and customer requests. Issue CSV does not include attachment files. Save any files, links and decisions the next owner needs separately.
An issue you accidentally deleted	Check Recently deleted in the team archive. Linear documents 30 days before a deleted issue is permanently removed.

What do teams pay for in Linear?

Free includes up to two teams and 250 issues, with unlimited members. Everyone in a Free workspace is an admin. Paid plans charge for unsuspended users in the workspace.

In November 2026, the listed annual rates were US$10 per user per month for Basic and US$16 per user per month for Business. Business and Enterprise add guest accounts and bill those guests as regular members. A guest gets access to the teams they’re added to. An enabled workspace integration can give guests access to Linear data from other teams. Check each connected tool’s permissions before inviting a guest.

Cloud coding sessions and automated Loops use a separate prepaid workspace balance. A cloud coding session can charge for model usage and the time its temporary coding environment runs. You can keep a backlog and review linked changes without starting a coding session.