Epic Goal

Improving customer's experience with using ACM and efficiently addressing and resolving reported issues.

Why is this important?

When a customer support case is open, the team needs to be able to triage and address any concerns within a timely manner. To ensure that we are able to monitor and commit to the support case throughout the sprint, this epic will allow us to track the progress and update on cases that come through the team's channels.

Scenarios

Customer A reports an uninstall issue; however, upon investigation, the case requires multiple weeks/days of debugging.

Acceptance Criteria

Customer support cases has been resolved for the current release.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• 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 Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>