-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
RHDH Jira triage maintainer agent
-
M
-
False
-
-
False
-
In Progress
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
0% To Do, 0% In Progress, 100% Done
-
-
EPIC Goal
Build an accurate, easy-to-use Jira AI triager agent that can be integrated into RHDH developer workflow for faster Jira team and component assignment. The aim is to reduce/eliminate the workload for the rotating Jira triage maintainer role.
Background/Feature Origin
Currently, there is a rotating triage maintainer role that rotates every sprint that requires a developer to take several context switches throughout the day to assign team/component to Jiras missing those fields. This task is time-consuming, repetitive, and distracts from regular sprint work.
Work off of this initial implementation as a result of the linked spike.
Why is this important?
- Makes ticket assignment more consistent and accurate
- Helps teams respond to issues faster
- Reduces time and effort required from traiger maintainer
User Scenarios
- A dev creates a Jira issue missing team and/or component assignment, the agent catches that issue and suggests the best fit.
- A triage maintainer runs the tool to batch approve and assign untriaged issues
Dependencies (internal and external)
- Jira API access
- Gemini API
- Access to historical Jira data
Acceptance Criteria
Release Enablement/Demo - Provide necessary release enablement details
and documents
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Playwright: <link or reference to playwright>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>
- is triggered by
-
RHIDP-8106 [Spike] Explore using AI to fulfill triage maintainer duties
-
- Closed
-