Skip to content

0001: Redefinition of Linear Issue Statuses

  • Status: ✅ Accepted
  • Date: 2025-11-03
  • Owners: @osmank, @onur, @enver
  • Context:
    The previous usage of Backlog, Planned, and Todo statuses in Linear created ambiguity during release planning. Specifically, Todo overlapped with Backlog as issues transitioned between cycles, making it unclear which issues were actually part of the active release versus those still being considered. The goal was to simplify and standardize the status model so that release planning, backlog grooming, and progress tracking remain clear and predictable.

Decision

We have redefined the relationship between issue statuses in Linear as follows:

  • Backlog: Represents issues that are identified but not planned for the current release. These include long-term improvements, deferred features, or pending ideas awaiting prioritization.
  • Planned: Represents issues actively selected for the current release cycle. Once work begins, the issue moves directly from Planned to In Progress (or the equivalent implementation status).

There is no longer an intermediate Todo state. If an issue is expected to be included in a future release but is not yet part of the current one, it remains in Backlog and should be tagged with next to indicate its upcoming priority.

This simplification ensures that:

  • Long-term and short-term priorities are distinctly visible.
  • Planning cycles remain transparent.
  • Status transitions are easier to automate and report on.

Options Considered

  • Option A – Keep existing definitions (no change)
    • Pros: No migration effort required.
    • Cons: Todo created overlap and confusion with Backlog; made transition rules unclear.
    • Decision: Rejected due to unclear separation between Todo and Backlog.
  • Option B – Simplify to Backlog and Planned
    • Pros: Clear hierarchy; less cognitive overhead; improved planning visibility.
    • Cons: Requires migration effort and adjustment of existing workflows.

Consequences

  • Positive:
    • Clearer and more predictable status transitions.
    • Reduced duplication between Backlog and Todo.
    • Easier release board visualization and automation logic.
    • Simplified planning and reporting workflows.
  • Negative:
    • One-time cleanup effort to migrate existing Todo issues.
    • Team habits and filters may need to be updated.
  • Follow-ups / migrations:
    • Review and update all current Linear issues to align with the new two-status model.
    • Remove Todo from all existing workflows.
    • Update internal documentation and team onboarding materials.