> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.islo.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.islo.dev/_mcp/server.

# Issue triage

> Investigate a reported bug and create a verified fix ticket.

Use the **Triage a bug** Suggested Line (`triage-bug`) when a report needs evidence before anyone changes code. It investigates the report, checks the reproduction independently, and writes an implementation-ready Linear ticket when the behavior is confirmed. This Line does not modify product code.

## Start with a report

1. Connect GitHub and Linear in [Manage → Integrations](https://app.islo.dev/integrations).
2. [Deploy the Suggested Line](/use-cases/suggested-lines) in your factory. Its Agents need a Machine that can access the repository.
3. Mention the Islo app in Slack with the symptom, reproduction steps, repository, and relevant logs or issue link. You can also start `triage-bug` manually with the report as its `input`.
4. Open the run to read the triage and verification results. If the behavior is confirmed, follow the Linear ticket created by the planning stage.

The Line uses a manual trigger. A Slack delegation can choose it for a bug report; the Line itself does not subscribe to every new issue. If the evidence is insufficient, the run reports what it tried instead of inventing a diagnosis.

To turn a verified ticket into a pull request, use [Feature delivery](/use-cases/feature-delivery). For a pull request whose CI already fails, see [Bug fix](/use-cases/bug-fix). To classify every incoming issue or use different routing rules, [build a custom Line](/use-cases/custom-lines).