Linear API English: Vocabulary for Engineering Project Management Discussions

Linear has become the project management tool of choice for many engineering teams, and it comes with its own vocabulary. If your team uses Linear for tracking work, understanding the specific terms — and the English phrases that surround them — will help you participate more clearly in planning meetings, status updates, and async discussions.

Core Vocabulary

Issue The fundamental work item in Linear. An issue represents a bug, a feature, a task, or any other unit of work that can be assigned, prioritised, and tracked through a workflow.

“Before you start coding, make sure the issue is linked to the current cycle so the team can see it in the sprint board.”

Cycle A time-boxed period of focused work in Linear, equivalent to a sprint in Scrum. Cycles typically last one or two weeks and contain a set of issues the team commits to completing.

“We’re closing the cycle on Friday — anything that isn’t done by then will be rolled over to the next cycle or moved back to the backlog.”

Project A goal-oriented grouping of issues in Linear that spans multiple cycles and works toward a specific outcome. Projects are higher-level than cycles and can track milestones.

“The authentication overhaul is a project that will take about six weeks — it spans three cycles and includes issues across the backend, frontend, and security teams.”

Roadmap A high-level, time-based view of projects and milestones in Linear, used to communicate strategic direction to stakeholders and other teams.

“I shared the roadmap with the product team this morning — they wanted to see which projects are planned for Q3 and what depends on the API redesign.”

Triage The process of reviewing incoming issues — typically bug reports or support escalations — to assess their severity, assign priority, and route them to the appropriate team or cycle.

“We run a triage session every Monday morning to review new issues that came in over the weekend before they pile up.”

SLA (Service Level Agreement) In Linear, SLA can refer to a target response or resolution time for issues, particularly for support-related workflows where customers expect a timely reply.

“The enterprise tier SLA requires us to acknowledge a SEV1 bug within two hours — we set up an alert in Linear to flag issues that are approaching the deadline.”

Priority levels Linear uses four named priority levels: Urgent, High, Medium, and Low, plus No Priority. These communicate how quickly an issue needs to be addressed relative to other work.

“I’ve marked the login failure as Urgent — it’s blocking users from accessing the product and needs to be picked up today, not in the next cycle.”

Status workflow The series of states an issue moves through in Linear, typically: Backlog, Todo, In Progress, In Review, Done, and Cancelled. Teams can customise these to match their process.

“The issue is stuck in In Review — can you check if your PR is ready for a second review? It’s been three days and the cycle is ending Friday.”

Label A tag applied to an issue in Linear to categorise it by type, component, or any other dimension. Labels are used for filtering, reporting, and at-a-glance context.

“We use labels like ‘frontend,’ ‘perf,’ and ‘customer-reported’ so we can filter the backlog quickly during planning.”

Team An organisational unit in Linear with its own backlog, cycles, workflow states, and member list. Large companies often have one Linear team per engineering squad.

“The issue is in the Platform team’s backlog — you’ll need to cross-post it or tag their team lead to get it prioritised on their side.”

Key Collocations

• file an issue — “If you spot a bug in production, file an issue immediately and add the ‘incident’ label so it shows up in our monitoring filter.”
• move to triage — “When a support ticket becomes a code problem, we move it to triage so the engineering team can assess severity and assign it.”
• close the cycle — “We close the cycle every Friday at 5pm — anything in progress gets a status update comment before we wrap up.”
• update the roadmap — “After the board meeting, we’ll need to update the roadmap to reflect the change in Q4 priorities.”
• assign priority — “The product manager will assign priority after triage — don’t start working on it until the priority is set.”
• mark as duplicate — “This bug has been reported three times — mark the newer ones as duplicate and link them to the original issue.”

Using This Vocabulary in Meetings

Linear’s vocabulary is designed for speed, and the most fluent Linear users speak in shorthand: “file it,” “triage it,” “close the cycle,” “add it to the roadmap.” Knowing when to use shorthand versus full phrases is a sign of fluency.

In status meetings, a common structure is: “Issue X is in review, blocking the cycle — can someone pick it up?” This combines status (in review), impact (blocking the cycle), and a call to action in one sentence.

When discussing scope changes, the phrase “scope creep” is common in Linear discussions: “This issue has turned into three issues — we need to break it up before it causes scope creep in the cycle.” Being able to identify and name scope creep helps teams keep cycles focused.

Practice Tip

At the end of your next sprint or cycle, write a brief summary in English using at least five terms from this article: mention which issues you closed, whether anything was moved to the next cycle, how triage went for any incoming bugs, and what the priority distribution looked like. Writing project management updates in English is excellent practice because it forces you to use these terms in realistic context, not just in reading exercises.