Goal

Today we have a few options across the UI that we can skip, and each has a different feel and look.

After this epic the skip flow would be consistent across different fields

DOCS

This ticket covers the documentation updates required for the standardization of "skip" interactions within the MTV User Interface. The objective is to ensure that when a user chooses to skip a specific field or configuration during the migration planning process, the workflow remains uniform and predictable across all UI components. This standardization aims to reduce cognitive load and enhance the overall user experience during complex migration setups.

Jobs to Be Done (JTBD)

• When I am configuring a migration plan or adding a provider in the MTV UI, I want to have a consistent and clear method for skipping non-mandatory fields or configurations, so that I can progress through the wizard efficiently without confusion regarding the result of that skip action.
   

User Stories

• As a VM owner/cluster administrator, I want to achieve a consistent skip interaction so that the UI is more uniform and I can clearly distinguish between optional and required steps during migration planning.
   
• As a Migration Plan creator, I want a standardized skip flow across different fields (such as network or storage mapping) to ensure that skipping one element does not inadvertently impact the validation state of the entire plan.

Overview

This documentation ticket tracks the updates required for the Migration Toolkit for Virtualization (MTV) 2.11 release to reflect the standardization of the "skip" interaction across the user interface. The goal of this UI enhancement is to provide a consistent, predictable workflow for users during the migration planning process, thereby reducing cognitive load.

Problem Statement

The "skip" interaction currently varies across different UI components in the MTV console. This inconsistency can lead to user confusion regarding how to bypass non-mandatory fields or configurations. Engineering is implementing a fix to ensure that skipping one element does not inadvertently impact the validation state of the entire migration plan.

Documentation Requirements

The technical writer must update the following documentation sets to reflect the new standardized behavior:

• Planning your migration to Red Hat OpenShift Virtualization:

• • Update procedures for creating migration plans to highlight the standardized method for skipping optional configurations (e.g., network or storage mapping steps that are not mandatory).

• Migrating your virtual machines to Red Hat OpenShift Virtualization:

• • Review and update wizard-based task instructions to ensure the "skip" action terminology matches the updated UI.

• Release Notes for MTV 2.11:

• • Include a summary of the improved user experience and the consistency of the skip interaction.

Technical Details

• Fix Version: 2.11.0.

• Target Components: Migration planning wizard and configuration forms.

• Dependencies: Successful documentation completion relies on the finalization of the technical approach and UI implementation within the parent Epic MTV-3978.

Job to be Done Statement

"When I am configuring a migration plan, I want to skip non-mandatory fields or configurations consistently across the UI, so I can complete the planning process efficiently without inadvertently affecting the validation state of my plan."