Value Statement

Currently, monitoring the status of Konflux still requires manual review, summary, and notification to the Slack channel. When a build issue occurs, the build owner must manually mention the relevant component squad members in the channel. We hope to automate these tasks with an intelligent Jira Agent, acting as a dedicated assistant for Konflux Jira. This agent will free us from tedious summary, notification, and information synchronization tasks, allowing us to focus on more complex and important issues.

Definition of Done for Engineering Story Owner (Checklist)

• Create a Jira Agent

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.