Value Statement

• Documentation that is no longer relevant clutters the doc, conflicts with feature changes, and confuses users.
• Keeping this current increases SEO, UX, conciseness, and accuracy.
• This is not for new documentation. This is an audit of existing documentation.

Procedure

Step 1: ACM/MCE dev teams please review the Known issues for outdated entries.
Step 2: Comment in your issue and tag your writer, OR send a PR and tag your writer if something needs to be removed or updated.
Step 3: Review the Deprecations table. If something has been removed, tag your writer in the comments so they can move it to the Removals table. You can also create a PR.
Step 4: Review the Troubleshooting topics for outdated entries.
Step 5: Comment in your issue and tag your writer, OR send a PR and tag your writer if something needs to be removed or updated.
Step 6: Place your Jira ticket in Review and the writer will close when all updates are made.

ACM Deprecations
https://github.com/stolostron/rhacm-docs/blob/2.15_stage/release_notes/acm_deprecate_remove.adoc#deprecations-removals-acm

MCE Deprecations
https://github.com/stolostron/rhacm-docs/blob/2.15_stage/clusters/release_notes/mce_deprecate_remove.adoc

ACM Known issues
https://github.com/stolostron/rhacm-docs/blob/2.15_stage/release_notes/acm_known_issues_intro.adoc

MCE Known issues
https://github.com/stolostron/rhacm-docs/blob/2.15_stage/clusters/release_notes/mce_known_issues.adoc

ACM Troubleshooting

https://github.com/stolostron/rhacm-docs/blob/2.15_stage/troubleshooting/troubleshooting_intro.adoc

MCE Troubleshooting

https://github.com/stolostron/rhacm-docs/blob/2.15_stage/clusters/support_troubleshooting/troubleshooting_mce_intro.adoc

Development Complete

Issues are all closed

-------------------------------------------------------------------------------------------------------
QE Hand Off Template (fill out when moving to Review) 11/25/25:

Summary of the Work:
What was implemented or fixed? Include a brief description of the problem (if applicable) and how it was addressed.
e.g., "Updated the UI to show validation errors for the form. The previous implementation did not surface backend validation issues."

Key Areas to Verify:

1. What functionality should QE focus on? List what was tested or what is most important to validate.
2. Ensure the new validation messages appear for required fields
3. Confirm the workflow still completes as expected after validation fixes
4. Any edge cases or high-risk areas touched by the change

Fix or Feature Availability:
When will this be available in a build?
Code merged on: YYYY-MM-DD
Expected downstream build tag (if known): example-build-tag
(Optional) Related PR(s): Link