How to Fix Linear Issue State (Status) Transitions Not Working

In this tutorial, you'll learn about How to Fix Linear Issue State (Status) Transitions Not Working. We cover key concepts, practical examples, and best practices.

Linear issue states (statuses like Todo, In Progress, Done) are configured in a workflow that defines which transitions are allowed. When a team member cannot move an issue to the expected state, the workflow restricts the transition, the user lacks permission, or the state was archived.

The Problem

You click the status dropdown on a Linear issue but the expected state (e.g., "In Review") is not in the list. Other team members see it.

Wrong approach — changing the issue type to a different workflow.

The Fix

Check the workflow configuration:

1. Linear → Settings → Workflows
2. Find the workflow used by the issue's team
3. Review the states in the workflow
4. If "In Review" is missing, add it to the workflow
5. Drag to position it between "In Progress" and "Done"

If the state exists but is not in the dropdown:

1. Edit the workflow → click the state
2. Check "Only certain teams can use this state" — it may be restricted
3. Set it to "All teams" or add the specific team
4. Save → refresh the issue page

For archived states:

1. In workflow settings, click "Show archived states"
2. Archived states are hidden from dropdowns
3. Unarchive the state to make it available again
4. Existing issues in archived states retain that state

Expected output:

All expected states appear in the issue dropdown
Team members can transition issues through the workflow
Workflow states are ordered logically (Todo → In Progress → Done)

Prevention Tips

• Design workflows before adding issues — changing workflows later can be confusing
• Limit workflows to 5-7 states to avoid dropdown overwhelm
• Use "Review" and "Approved" states for teams with QA processes
• Archive unused states instead of deleting them (deleting removes state from existing issues)
• Document workflow guidelines so the team understands each state's meaning

Common Mistakes with issue state

1. Overlapping type class instances that cause GHC to reject the program with ambiguous dispatch errors
2. Non-exhaustive pattern matches that compile with warnings then crash at runtime
3. Misunderstanding that String is [Char] with poor performance for large text operations

These mistakes appear frequently in real-world LINEAR code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

Related: DodaTech's Linear Workflow Analyzer reviews active workflows, identifies bottlenecks (states with too many issues), and recommends workflow optimizations for faster delivery. Use with DodaZIP for backup.