Uploaded image for project: 'Migration Toolkit for Applications'
  1. Migration Toolkit for Applications
  2. MTA-1815

[Regression][Migration wave] First valid value of Start Date and End Date is not marked

    • False
    • Hide

      None

      Show
      None
    • False
    • Yes

      Description of problem:

      When selecting start date or end date for a new migration wave, the first valid value is not marked as it used to be.

      Version-Release number of selected component (if applicable):

      mta-operator-bundle-container-7.0.0-46

      How reproducible:

      100%

      Attachments:

      migration_wave_mta-7.0.0-46.png
      migration_wave_mta-6.2.1.png

        1. migration_wave_mta-6.2.1.png
          migration_wave_mta-6.2.1.png
          73 kB
        2. migration_wave_mta-7.0.0-46.png
          migration_wave_mta-7.0.0-46.png
          73 kB
        3. mta-7.0.0-47.mp4
          1.10 MB
        4. mw_konveyor_v0.3.0-rc.3.mp4
          818 kB

            [MTA-1815] [Regression][Migration wave] First valid value of Start Date and End Date is not marked

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Migration Toolkit for Applications bug fix and enhancement update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHBA-2024:0599

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Migration Toolkit for Applications bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2024:0599

            Thanks ibolton@redhat.com
            Since it is a PF bug and occurs only when the start date is set to the end of the month, we can close this ticket and I will keep tracking the PF bug

            Moved to Verified.

            Version:
            upstream konveyor v0.3.0-rc.3

            Maayan Hadasi added a comment - Thanks ibolton@redhat.com Since it is a PF bug and occurs only when the start date is set to the end of the month, we can close this ticket and I will keep tracking the PF bug Moved to Verified. Version: upstream konveyor v0.3.0-rc.3

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in a merge request of rhmt / MTA Midstream on branch mta-7.0-rhel-9_ upstream _216ece6df086c46532e50ece45e07ce5 : Updated 8 upstream sources

            Ian Bolton added a comment - - edited

            This appears to be an issue with how the patternfly datepicker behaves. https://www.patternfly.org/components/date-and-time/date-and-time-picker#date-and-time-range-picker You can reproduce this behavior in the patternfly docs. The Datepicker component seems to have a bug in cases when the end date begin range is not the same as the start date. PF bug filed -> https://github.com/patternfly/patternfly-react/issues/9933 

            Ian Bolton added a comment - - edited This appears to be an issue with how the patternfly datepicker behaves. https://www.patternfly.org/components/date-and-time/date-and-time-picker#date-and-time-range-picker You can reproduce this behavior in the patternfly docs. The Datepicker component seems to have a bug in cases when the end date begin range is not the same as the start date. PF bug filed -> https://github.com/patternfly/patternfly-react/issues/9933  

            Tested with upstream konveyor v0.3.0-rc.3, and there seems to be an edge case when the startDate is the end of the month
            Please see recording: mw_konveyor_v0.3.0-rc.3.mp4

            Moved to ASSIGNED.

            Maayan Hadasi added a comment - Tested with upstream konveyor v0.3.0-rc.3, and there seems to be an edge case when the startDate is the end of the month Please see recording: mw_konveyor_v0.3.0-rc.3.mp4 Moved to ASSIGNED.

            Ian Bolton added a comment -

            Ian Bolton added a comment - https://github.com/konveyor/tackle2-ui/pull/1632

            Tested with mta-7.0.0-48 - the issue is not fixed for the End Date datepicker

            Moved to ASSIGNED.

            Maayan Hadasi added a comment - Tested with mta-7.0.0-48 - the issue is not fixed for the End Date datepicker Moved to ASSIGNED.

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in a merge request of rhmt / MTA Midstream on branch mta-7.0-rhel-9_ upstream _969264b109075b54d9ac9a1df4db36f7 : Updated 8 upstream sources

            Ian Bolton added a comment -

            Ian Bolton added a comment - https://github.com/konveyor/tackle2-ui/pull/1613

            Tested with mta-7.0.0-47 - the first valid date value is not always marked. Please see recording: mta-7.0.0-47.mp4

             Moved to ASSIGNED.

            Maayan Hadasi added a comment - Tested with mta-7.0.0-47 - the first valid date value is not always marked. Please see recording: mta-7.0.0-47.mp4  Moved to ASSIGNED.

              ibolton@redhat.com Ian Bolton
              mguetta1 Maayan Hadasi
              Maayan Hadasi Maayan Hadasi
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: