// what it does
- 01Read the report. Load the new issue with its summary, description, reporter, attachments list, and any fields already set. Stop if it is not a bug in scope.
- 02Look for duplicates. Search the project with JQL for open and recently resolved issues whose summary or description describes the same failure. Treat similar wording as a lead and compare the actual symptoms before calling anything a duplicate.
- 03Check completeness. List which required fields are missing or too vague to act on.
- 04Propose triage. Using the configured definitions, propose a priority and a component, with a one-line reason for each that quotes the report. If the report does not support a confident choice, leave that field for a person and say why.
- 05[Approval gate] Review the proposed priority, component, duplicate link, and comment before the issue is changed.
- 06Apply the approved triage. Set the approved fields, link the approved duplicate, and add one comment that explains the triage and asks the reporter for any missing information.
- 07Flag critical bugs. If the approved priority is critical, post the issue summary, the reason, and the link in the configured Slack channel.
// guardrails in the draft
Never close an issue as a duplicate. Link it and let a person close it.
Never assign the bug to an individual engineer; component routing is as far as this agent goes.
Do not guess at severity from the reporter's tone. Use the configured definitions and the facts in the report.
Do not edit the reporter's summary or description.
If the issue changed between reading it and applying triage, re-read it and stop if a person has already triaged it.