# From report to fix

> What happens to a report sent from your editor: the hourly triage, public issues in elide-dev/elide, +1s on duplicates, draft benchmark cases, and tracking with report_status.

An accepted report becomes a public issue in [elide-dev/elide](https://github.com/elide-dev/elide/issues), usually
within the hour.

1. The agent calls `preview_report`: secrets and personal data are stripped, duplicates checked, and a preview
   returned. Nothing is sent.
2. You confirm, and `submit_report` puts the report in the queue.
3. An hourly triage job reads the queue.
4. Each report becomes a public issue, a +1 on an existing issue, a draft benchmark case, a docs fix, or goes to human
   review.
5. `report_status` reads the status back to the agent.

## Outcomes

| Outcome | When |
| --- | --- |
| New public issue | The report is new. Labels: `intake` and `kind:<kind>`. |
| +1 on an existing issue | The problem is already reported. |
| Draft benchmark case | A `perf` report includes a repro. |
| Docs fix | The docs were wrong or missing. |
| Human review | Triage can't decide. |

## Track a report

Call `report_status` with the id `submit_report` returned. It reports the state and, once triaged, the issue URL.

Follow issues with the `intake` label at
[elide-dev/elide](https://github.com/elide-dev/elide/issues?q=label%3Aintake). For immediate help, ask on Discord at
https://elide.dev/discord.