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

HCC operator search/discoverability for operators (except RHACS)

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Center-UI-Team
    • None
    • HCC operator search/discoverability
    • True
    • Hide

      Search cannot be done until RHCLOUD-33627 is complete

      Show
      Search cannot be done until RHCLOUD-33627 is complete
    • False
    • To Do
    • XCMSTRAT-1204 - Improve operator discoverability in OCM UI phase 2
    • 83% To Do, 0% In Progress, 17% Done

      Description

      As a user, I want to more easily find related operators (with the exception of RHACS) within the HCC search and products section.

      Acceptance criteria

      The following products/operators shall be available when a user searches the HCC search bar:

       

      When the user views the HCC product drop down or goes to the services page All services page (https://console.redhat.com/allservices). There is a section for "Operators"

       

      When the user views the HCC product drop down or goes to the services page All services page (https://console.redhat.com/allservices), under "Operators" there is a entry for each of the following:

      Areas Impacted

      Search

      Product drop-down

      All services page (https://console.redhat.com/allservices)

      Out of scope

      Any changes to OCMUI app functionality.

      Testing implications

      Unsure what team, if any, is responsible for testing changes.  Determined that it should be HCC team.

      ------------------------------------------------------------------------------------------------------------------------

      Implementation notes

      There are two ways to add items to HCC search/product page. The first is to use the FEC utility and front-end operator (outlined in OCMUI-3330):

      1. Onboarding to the FEC utility (POC shared in F2F): https://github.com/RedHatInsights/uhc-portal/compare/master...florkbr:uhc-portal:hcc-fec-build-tool-poc?expand=1
      2. Updating to use the new frontend operator features (self service): https://github.com/RedHatInsights/chrome-service-backend/blob/main/docs/feo-migration-guide.md

      The second is to use the legacy method which would involve making a PR in the https://github.com/RedHatInsights/chrome-service-backend repo.

      1. Adding search entries (legacy): https://github.com/RedHatInsights/chrome-service-backend/blob/main/docs/search-index.md#adding-entries-to-search-index
      2. Adding allservices entries (legacy): https://github.com/RedHatInsights/chrome-service-backend/blob/main/docs/cloud-services-config.md#all-services-dropdown-and-page

      The expectation is that, right now, the second (legacy) approach would be taken.

      More information needed

      There are content questions that need to be addressed before implementation including:

      • What is the description for each entry?

        1. Screenshot 2025-04-21 at 4.12.26 PM.png
          91 kB
          Kim Doberstein
        2. Screenshot 2025-04-21 at 4.13.43 PM.png
          208 kB
          Kim Doberstein
        3. Screenshot 2025-04-21 at 4.14.44 PM.png
          214 kB
          Kim Doberstein

              Unassigned Unassigned
              kdoberst Kim Doberstein
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: