Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-2570

[Cluster history] The date filters were not reset when a new cluster definition opened from OCM UI

    • False
    • Hide

      None

      Show
      None
    • False
    • OCMUI Core Sprint 261, OCMUI Core Sprint 262

      Description of the Problem

      User has opened a cluster and went to cluster history then set the date filters i.e. "from" and "to" dates and searched some history. After the same action, user has opened another cluster from the list (it is common workflow if you are org admin) and went to cluster history section. The user has seen the date filters are preserved based on previous selection. This is wrong behavior. The date filters (both from and to fields) should reset to the present date and show the cluster history based on the same.

      See the recordings Screencast from 2024-10-24 16-04-03.mp4

      How reproducible:

      always

      Steps to Reproduce:

      1. Open OCM UI staging.
      2. Open a ready cluster.
      3. Go to cluster history tab, Set the "from" and "to" date filters other than default.
      4. Review the cluster history.
      5. Open another ready cluster.
      6. Go to cluster history tab and see the cluster history and filters.

      Actual results:

      At Step 6, the cluster history filters are set based on previous filters set (At step 3) on another cluster.
      The cluster history  filters should be reset  to default definition when a new cluster definition opened from OCM UI. 

      Expected results:

      At Step 6, The cluster history date filters should set based on the present date not based on the previous filters set on different cluster.

              emingora Enrique Mingorance Cano
              jmekkatt@redhat.com Jayakrishnan Mekkattillam
              Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: