The underlying feature (Epic MTV-3712) enhances the visibility and interpretation of pre-migration concerns/validations shown for individual VMs within a migration plan. The existing implementation was confusing: users often couldn't tell if a detected concern meant the entire plan would fail, only that VM would fail, or if the concern was merely a warning that could be safely ignored.

Technical Writer Scope

The primary objective is to document the new, clarified taxonomy and visual indicators for migration concerns. Key documentation areas include:

1. New Concern Taxonomy: Document the new system for classifying migration issues (e.g., distinguishing between Hard Stops/Fatal Errors, VM-Specific Failures, and Ignorable Warnings).

1. UI Alignment: Review the new visual indicators (icons, colors, and associated textual summary) on the plan details page and migration wizard to ensure documentation screenshots and descriptions match the new clarity.

1. Actionable Guidance: For each major concern type, provide explicit guidance on the required user action (e.g., "Must be fixed," "Can be ignored but will result in manual configuration post-migration," or "Plan execution will stop").

1. Integration: Update the Migration Plan Creation and Migration Monitoring/Troubleshooting chapters to reference this new, clearer concern display, enabling the user to make immediate, informed decisions.

JTBD Statement:

"When I review the readiness of a migration plan, I want every potential issue (concern) to be clearly categorized by its impact so that I can immediately know if a VM will fail, if the whole plan is blocked, or if it is a minor warning, allowing me to make informed, pre-migration decisions and ensure my migration is successful on the first attempt."

Documentation Task

The documentation task (MTV-3714) supports this job by addressing the primary sub-job:

"When the new concern taxonomy is implemented, I need documentation that defines the meaning of every icon, color, and label so that I can quickly and accurately interpret the severity of a validation issue and know the precise action required to fix it."

Goal

Today we do show concerns about each VM in a plan, but it might be confusing to understand if those concern will fail the migration/ will only the vm fail to migrate or will it migrate succesfully.

After this epic we will be able to understand in a better way which problems I have in each vm and figure if it's affecting the entire plan/only the vm or few of the vms share the same concern

User Stories

• As a cluster administrator,
  I want to know easily if my plan will migrate all vms properly before I start migrating or is there some issues that needs to be fixed/can't be fixed at all,
  so that I can make the needed actions to make my migration successful on the first attemp

Non-Requirements

• <anything that we explicitly exclude>

Notes

• UX design doc: https://docs.google.com/document/d/1vFtSGNd-KjTzLs-ybwno51H4RLhhaVBf9Pgu-O7u5E4/edit?tab=t.0#heading=h.xt0a54zmwy