English for Linear Issue Tracking

Linear popularized a specific set of project-management terms — “cycle” instead of “sprint,” “triage” as a distinct queue, “sub-issue” for hierarchical breakdown — that teams new to the tool often misuse out of habit from Jira or Trello. Getting this vocabulary right makes stand-ups and planning conversations sharper. This guide covers the essential terms.

Key Vocabulary

Cycle — Linear’s term for a time-boxed iteration (equivalent to a sprint elsewhere), during which a team commits to completing a set of issues. “We’re carrying three issues over into the next cycle since they weren’t finished this week.”

Triage — a dedicated queue for new issues that haven’t yet been assigned, prioritized, or added to a cycle, used to review incoming work before it enters the workflow. “That bug report just landed in triage — someone needs to review it and decide if it’s this cycle’s problem or backlog.”

Sub-issue — a smaller issue nested under a parent issue, used to break down large work items without losing the connection to the overall task. “Instead of one giant issue for the migration, we split it into five sub-issues so we can track progress on each piece independently.”

Workflow state — the status column an issue sits in (Backlog, Todo, In Progress, In Review, Done, Cancelled), representing where it is in the team’s process. “Move this to the ‘In Review’ workflow state once the PR is up, not before.”

Project — a larger initiative that groups related issues and cycles together, often spanning multiple cycles, with its own timeline and lead. “The onboarding redesign is a project that will span the next three cycles, not something we’ll finish in one.”

Roadmap — a higher-level view showing projects and their target dates across a longer time horizon, used for cross-team planning. “Let’s add this project to the roadmap so other teams can see it’s targeted for next quarter.”

Common Phrases

• “Is this issue triaged yet, or is it still sitting in the queue?”
• “Should we break this into sub-issues before adding it to the cycle?”
• “What workflow state is this in — has the PR actually gone up?”
• “Is this issue part of a project, or is it standalone?”
• “Are we carrying this over to the next cycle, or cutting scope?”

Example Sentences

Discussing scope in a planning meeting: “This issue is too large for one cycle — let’s split it into sub-issues so we can commit to the first two this cycle and push the rest to the next one.”

Reviewing triage in a stand-up: “There are five new issues in triage from yesterday — two look like duplicates of an existing bug, and the other three need a priority label before we can plan around them.”

Reporting project status to a stakeholder: “The project is on track according to the roadmap — three of the five cycles are complete, and the remaining sub-issues are all in progress or in review.”

Professional Tips

• Say “cycle” rather than “sprint” when working in Linear — using the wrong tool’s vocabulary in written updates signals unfamiliarity with the team’s actual process.
• Treat triage as an active queue that needs regular attention, not a place issues disappear to — mention it explicitly in stand-ups if it’s backing up.
• Use sub-issues to communicate scope, not just to organize — a parent issue with five open sub-issues clearly signals more remaining work than a vague single ticket.
• Distinguish a project from a cycle when reporting status — a project spans time, a cycle is a fixed window, and stakeholders need to know which one you’re referring to.

Practice Exercise

1. Explain in two sentences the difference between a cycle and a project in Linear.
2. Write a one-sentence stand-up update describing an issue still sitting in triage.
3. Describe, in your own words, why breaking a large issue into sub-issues helps track progress.

Navigating Nuances: Beyond Literal Translations

Linear’s strength lies partly in its visual flow and concise terminology – a deliberate choice to avoid overly verbose project management jargon. However, for non-native English speakers, translating those terms precisely can be tricky. It’s not just about knowing what “triage” means; it’s understanding how it’s used in a professional context, particularly when communicating with stakeholders who may have different assumptions. A simple definition won’t cut it – you need to convey the underlying process and expected behavior. For instance, saying “we’re triaging these issues” sounds more authoritative than “we’re sorting through these problems.” Similarly, understanding that a ‘sub-issue’ isn’t just a smaller version of the main issue but an independent piece of work contributing to the overall cycle is critical.

The key is to build your vocabulary around action verbs and clear expectations. Instead of simply stating an issue is “blocked,” consider phrases like “the issue is currently blocked due to dependencies on Team Alpha” or “we’re investigating the reason for the blockage.” This provides context, explains why it’s blocked, and implicitly communicates what needs to happen next. Similarly, when discussing cycle status – “cycle in progress,” “cycle completed,” “cycle paused” – think about the implications. Does “paused” mean temporarily halted, or does it signal a need for further investigation? Clarity here reduces misunderstandings and accelerates decision-making. Don’t be afraid to ask clarifying questions; asking “Can you elaborate on what needs to be done to move this issue forward?” is far more effective than silently struggling with the terminology.

Furthermore, pay attention to the language used in Linear itself – the labels for workflow states, the descriptions of sub-issues, and the prompts within the interface all contribute to a shared understanding. This isn’t just about learning individual words; it’s about absorbing the culture of communication surrounding the tool. Recognizing that “investigation” is often used in conjunction with blocked issues is as important as knowing what “blocked” means.

Finally, remember that documentation and communication are your allies. Refer back to Linear’s help resources, consult with colleagues who are comfortable using the terminology, and don’t hesitate to clarify any uncertainties you encounter.

# Example: Using 'linear close' command to resolve an issue
linear issue close --comment "Resolved as per discussion.  Dependencies addressed." 123

This command demonstrates a simple action – closing an issue – but the added comment illustrates how professional language and context are layered onto a basic operation, reflecting the more nuanced communication expected within Linear’s workflow.