Uploaded image for project: 'Migration Toolkit for Virtualization'
  1. Migration Toolkit for Virtualization
  2. MTV-2861

[UI] the UX for plan creation wizard and plan tabs is sometimes different and not consistent

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Normal Normal
    • None
    • 2.9.0
    • User Interface
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False

      The look and feel of exact  same settings in different places in MTV UI is not consistent without any real reason for that. It makes the UI confusing.

       

      Examples:

      1. the plan creation - mapping step and existed plan -> mappings tab is not consistent:

      When user clicks on "Add mapping" button for adding another mapping entry - 

      in create plan wizard - an empty mapping row is added for every click

      in plan - mapping tab - an prefilled mapping row (of calculated next entry) is displayed for every click

       

      2. The look and feel of the plan creation - hooks step and existed plan -> hooks tab is not consistent:

      a. Selecting the step is a by a checkbox in wizard and a switch in hooks tab

      b. 'Hook runner image' field is mandatory in hooks tab with an initial default value  of 'quay.io/konveyor/hook-runner' is displayed, while it's  not mandatory in create plan with an empty default value

      c. The help text for the 'Ansible playbook" field is different.

       

      3. Tooltips are different for various settings in create plan and plan details. For example: tooltips of 'Preserve static IPs' field is different. Need to choose one tooltip  rephrasing and use in both places.

       

      4. Entering an "edit" mode is different and very confusing when comparing the plan - hooks tab and plan - mappings tab:

      Within the plan's mapping tab - the flow for editing the mapping of an existing plan is:

      a. Clicking on the "Update mappings" button for entering the edit mode (if edit is permitted).

      b. Make the required changes

      c. Click "update mappings" if the change is valid or click "cancel"

       

      Within the plan's hooks tab - the flow for editing the hooks of an existing plan is:

      a. Edit the existing hooks settings, if permitted.

      b. If a change was done, the "Update hooks" button is enabled.

      c. Clicking on this button or click "cancel"

       

      Need both tabs to behave the same. either canceling the "update mappings" button for entering an edit mode or adding such a button in hooks tab as well.

        1. Screencast from 2025-07-21 20-13-59.webm
          179 kB
          Sharon Gratch
        2. Screencast from 2025-07-21 20-13-59-1.webm
          179 kB
          Sharon Gratch
        3. screenshot-1.png
          84 kB
          Sharon Gratch

              sgratch@redhat.com Sharon Gratch
              sgratch@redhat.com Sharon Gratch
              Matan Schatzman Matan Schatzman
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: