New bug reports arrive half-complete and land on whoever is on triage duty. An Orkeste agent reads each new bug in Jira, comments with the likely component, a severity assessment and a suggested owner, asks for missing reproduction steps and posts the critical ones to your engineering channel.
The problem
Triage takes an hour a day from a senior engineer. Bugs wait without a severity, duplicates go unnoticed and the critical one is found in the afternoon.
How the workflow runs
Runs: Every hour, or when you start it.
Find new bugs: The agent runs a JQL search for bugs created since its last run, up to ten per search.
Read each bug: It reads the summary, the description and the reproduction steps.
Assess: It names the likely component, the severity and a suggested owner from its briefing, and lists missing information.
Look for duplicates: It searches Jira for similar open issues and mentions them.
Comment and alert: It adds its assessment as a comment and posts critical bugs to the engineering channel in Slack.
The lead decides: The engineering lead sets the priority, the assignee and the sprint in Jira.
The agent comments and alerts; priority, assignee and sprint stay with the engineering lead. Comments can also wait in Validations.
Who does what
Bug triage agent: Reads new bugs and comments with its assessment.
Engineering lead (human): Sets priority, assignee and sprint.
What this workflow does not do
Does not change status, priority, assignee or sprint.