Give Triage an owner, let pull requests move issue status, and review cycle carryover, so Linear's board matches what is shipping without anyone chasing updates. Decide those settings in the first week, then check the board every week.
When you need this
- You are setting up Linear for the first teams, or it is in use and the board drifts from what is shipping.
- Requests arrive from Slack, support, and other teams with no single place to sort them.
- Leaders ask engineers for status that the tracker should already show.
Evaluation criteria
Shape teams around how work is owned
Which groups own a backlog and a rhythm of their own?
Look forCreate one team per group that plans together. On Business and Enterprise, use sub-teams when a group needs its own team inside a parent with inherited cycles and labels. Linear issue identifiers belong to the team, so an agent assigned ENG issues sees every ENG project. Scope instructions by project or label as well.
Give Triage an owner
Who decides what happens to work that arrives from outside the team?
Look forTurn on Triage for each team so issues from Slack, Sentry, and people outside the team enter an inbox. The owner accepts, declines, merges duplicates, or snoozes issues. Rotate the owner with Linear's Triage responsibility setting. Sourcebot routes every GitHub bug report into Linear with a Bug label and sets 2-day and 7-day SLAs by priority.
Let pull requests move status
Does anyone still drag cards by hand?
Look forGitHub or GitLab connected, with branch names copied from Linear issues. Team status automation set for pull request opening, review requests, and merge, and rechecked after every workflow change. One team's merge-to-dev automation stopped moving issues to In Staging for several weeks while merge-to-main kept working.
Use cycles as a rhythm
How long is a cycle, and what happens to unfinished work?
Look forCycles are optional per team, last 1 to 8 weeks, and roll open issues into the next cycle. A capacity dial estimates from the last three cycles' velocity. A Hacker News commenter who planned in another agile tracker for years found rollovers pushed cycles past capacity with no rebalancing, so review carryover at the start of each cycle. Turn off the optional automation that adds active issues to the current cycle if part-time members' work should stay out of it.
Put projects and initiatives above issues
Where does a leader see progress without asking?
Look forProjects for multi-cycle work and initiatives for company objectives, which every member except guests can see. Cross-team metrics come from Insights on Business or Dashboards on Enterprise.
Bring customer evidence in
Which requests came from which customers?
Look forTurn on Customer Requests. Intercom, Zendesk, Front, or Asks then add a request that links back to the source, so product teams can filter issues by customer count, tier, or revenue.
Check the board weekly
Is the board still true?
Look forA weekly check of Triage age, cycle carryover, and In Progress issues without linked pull requests. Xiaofei Du's ten-person team stopped trusting its board after the backlog went stale and sprints exceeded capacity.
Questions to ask vendors
- Who owns Triage for each team this week, and how fast must an issue leave it?
- Which pull request events move which statuses in each team?
- Do we use cycles, and who reviews carryover at the start of each one?
- Which projects roll up to which initiatives, and who updates them?
- Which customer-facing tools file into Triage, and which team receives them?
Red flags
- Issues In Progress with no linked branch or pull request.
- A Triage inbox nobody owns.
- Cycles that start above capacity because carryover is never reviewed.
- A backlog of issues nobody has touched in months.
- Status reports written by hand from data the tracker already holds.
Products in this piece
Sources
- Official documentation
- 9
- Public source
- 4
- Linear docs: Triage
- Linear docs: GitHub
- Linear docs: GitLab
- Linear docs: Cycles
- Linear docs: Sub-teams
- Linear docs: Initiatives
- Linear docs: Insights
- Linear docs: Dashboards
- Linear docs: Customer Requests
- Sourcebot: How we reached bug zero using Linear (Feb 19, 2026)
- GitHub issue on linear/linear: pull request merge automations stopped moving issue status (Sep 9, 2026)
- Hacker News: Linear cycles roll unfinished work forward without rebalancing (Aug 8, 2025)
- Xiaofei Du: We stopped paying for Linear (Aug 17, 2026)