Value Statement

场景：

1. In a release scrum meeting, the release manager will use this board to track the progress and issues encountered by the entire team in Konflux builds across multiple releases. The board also provides visibility into the resolution status, responsible owners for each issue, and whether any blockers exist.

2. The manager can use the Konflux dashboard to clearly see the team's efforts (story numbers, story points) dedicated to solving Konflux issues for each

Definition of Done for Engineering Story Owner (Checklist)

The board is created and used by release managers.

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.