triage-issue

You can triage Jira bugs by providing the raw bug report details. The assistant extracts key signals like error signatures and environment, searches for duplicates within the last 90 days, and returns a structured verdict recommending whether to create a new issue or add context to an existing ticket.

The best way to add context to an existing Jira bug ticket is to append extracted environment details, error signatures, and impact assessments directly to the matching issue. This assistant identifies the duplicate ticket during triage and automatically appends the new report's context to accelerate resolution.

Yes, you can automatically create Jira issues from raw bug reports when no duplicates are found. The assistant triages the report, extracts key signals like component and environment data, searches for existing issues within 90 days, and creates a well-structured new bug ticket if no matches surface.

Yes, Jira triage considers fix history when identifying duplicate bugs. The assistant surfaces duplicates within the last 90 days across error-focused, component-focused, and symptom-focused angles, and evaluates prior fix history to determine whether to comment on an existing ticket or create a new issue.

To start triaging bugs in Jira, you need to provide the raw bug report details. The assistant captures context such as error details, environment information, impact assessment, and related issues to extract key signals and perform multi-angle duplicate searches.