How to Fix Linear Triage Workflow Not Capturing Incoming Issues

In this tutorial, you'll learn about How to Fix Linear Triage Workflow Not Capturing Incoming Issues. We cover key concepts, practical examples, and best practices.

Linear's triage workflow automatically captures new issues and routes them to a triage queue for review. When the triage queue is empty or new issues bypass triage, the triage workflow is not enabled for the team, the auto-triaging rules are misconfigured, or the issue creator has triage bypass permission.

The Problem

You expect new issues to go to the triage queue for review, but they appear directly in the team's "Todo" or "Backlog" state instead. The triage view shows "No issues."

Wrong approach — manually moving each new issue to the triage state.

The Fix

Enable triage for the team:

1. Linear → Settings → Teams → select your team
2. Scroll to "Triage" section
3. Toggle "Enable triage" to ON
4. New issues from external sources (email, API, forms) will enter triage

Configure auto-triaging rules:

1. Settings → Teams → select team → Triage
2. Click "Add rule" — define conditions (label, priority, project)
3. Set action: "Automatically accept" or "Send to specific person"
4. Rules run when new issues enter the triage queue

If the issue creator bypasses triage:

1. Users with "Bypass triage" permission skip the queue
2. Settings → Teams → Permissions
3. Remove "Bypass triage" from users who should go through triage
4. Team admins and creators of the team can be configured differently

Expected output:

New issues appear in the triage queue for review
Assigned triage members can accept, reject, or reassign issues
Auto-triaging rules route common issues automatically

Prevention Tips

• Enable triage for teams that receive issues from external sources (emails, forms, API)
• Use auto-triaging rules to automatically accept issues from known patterns
• Assign a rotating triage person for each week
• Review the triage queue at least once daily
• Archive or reject issues that are duplicates or out of scope during triage

Common Mistakes with triage workflow

1. Mixing let bindings with <- bindings in do notation, producing type errors
2. Overlapping type class instances that cause GHC to reject the program with ambiguous dispatch errors
3. Non-exhaustive pattern matches that compile with warnings then crash at runtime

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 Triage Efficiency Analyzer tracks triage response times, queue volume trends, and auto-triaging accuracy to optimize your triage workflow. Use with DodaZIP for backup.