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

[OCM UI][Data sovereignty] filtered cluster list results by name or id didn't retained once user navigates to cluster details then back to cluster list.

    • False
    • Hide

      None

      Show
      None
    • False
    • ACM Console Sprint 258

      Description of problem:

      In multiregion enabled cluster list, user has applied a filter by name in the cluster list. Once filtered results are shown, randomly visited to one of the cluster details page and came back to cluster list again. Unfortunately  the filter by name  was cleared and the results were shown based on that. This looks wrong while compare to non multregion cluster list as well as from user experience. It would be good to retain the filter applied with cluster name or id.
      Note: Other filters such as "view only my clusters" or filter by cluster type retained as expected. 

      See the recording attached. Screencast from 2024-07-31 16-12-31.mp4

       

      How reproducible:
      always

      Steps to Reproduce:

      1. Open OCM UI staging using https://console.dev.redhat.com/openshift/?multiregion=true 
      2. Go to cluster list and  type  partial cluster name in filter by name or id field.
      3. Click one of the cluster from filtered cluster list.
      4. Once cluster overview page has shown , go back to cluster list (use breadcrumb options or  browser back button)
      5. See the behavior.

      Actual results:

      At step5, Previously set cluster filter i.e. partial cluster name in the "filter by name or id" was cleared and filter results are not retained from cluster list. 

      Expected results:

      Cluster list filter should retain based on the search done at step 2 even after step4.

       

            kdoberst Kim Doberstein
            jmekkatt@redhat.com Jayakrishnan Mekkattillam
            Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: