Value Statement

Provide customers with a quick way to provide UI feedback for ACM/MCE or to open support cases. This will allow us to react to customer desires and concerns more quickly and aligns our experience with OCM and ACS.

Definition of Done for Engineering Story Owner (Checklist)

• Feedback link is accessible from every MCE/ACM UI page
• The link launches a modal from which the user can access a feedback or support request form
• The feedback link does not interfere with any existing page controls
• The feedback link is accessible, meaning it can be accessed via keyboard navigation and has appropriate labels for screen readers
• Feedback form specifies both source (acm) and version query params

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.