-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Observability DOC content improvements
-
False
-
None
-
False
-
Not Selected
-
To Do
-
0% To Do, 50% In Progress, 50% Done
Epic Goal
Customers, support, and engineering would all benefit from some reorganization of the Obs doc portal.
Why is this important?
Self-service, ie serviceability, is a very important factor in customer satisfaction. DOC are the source of truth and should be highly regarded for ease of use and content.
Scenarios
As an ACM Observability user I want to be able to quickly understand the overall feature set and what value it can provide me.
As an ACM Observability user I need to find the relevant information easily and from a logical layout and flow that is intuitive.
As an ACM Observability user I will likely use Google as my first entry point to any RHACM DOC, so I expect SEO to play a role here.
Acceptance Criteria
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
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 - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable.
