• Icon: Feature Feature
    • Resolution: Done
    • Icon: Normal Normal
    • ACM 2.12.0
    • None
    • Search
    • False
    • None
    • False
    • Not Selected
    • 0% To Do, 0% In Progress, 100% Done

      Feature Overview

      Customers have a need to discover and learn about their fleet of clusters, their app deployments, their operator installations, and everything in between.

      Today, ACM Search is tucked under a left nav entry "Home". This makes search quite hidden.

      We think ACM Search should be everywhere, on every lifecycle component page, even perhaps an icon in the header bar itself. 
      We think ACM Search should be the way to interface with datas in a table output on every page where a list/table is needed.

      Goals

      • Make Search available directly from every ACM console page
      • Make Search available from the header bar

      Requirements

      This Section: A list of specific needs or objectives that a Feature must
      deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
      If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
      it does not shift the feature.

      Requirement Notes isMvp?
      CI - MUST be running successfully with test automation This is a
      requirement for ALL features.
      YES
      Release Technical Enablement Provide necessary release enablement details
      and documents.
      YES
           

      (Optional) Use Cases

      This Section:

      • Main success scenarios - high-level user stories
      • Alternate flow/scenarios - high-level user stories
      • ...

      Questions to answer

      • ...

      Out of Scope

      Background, and strategic fit

      This Section: What does the person writing code, testing, documenting
      need to know? What context can be provided to frame this feature?

      Assumptions

      • ...

      Customer Considerations

      • ...

      Documentation Considerations

      Questions to be addressed:

      • What educational or reference material (docs) is required to support this
        product feature? For users/admins? Other functions (security officers, etc)?
      • Does this feature have a doc impact?
      • New Content, Updates to existing content, Release Note, or No Doc Impact
      • If unsure and no Technical Writer is available, please contact Content
        Strategy.
      • What concepts do customers need to understand to be successful in
        [action]?
      • How do we expect customers will use the feature? For what purpose(s)?
      • What reference material might a customer want/need to complete [action]?
      • Is there source material that can be used as reference for the Technical
        Writer in writing the content? If yes, please link if available.
      • What is the doc impact (New Content, Updates to existing content, or
        Release Note)?

            sberens@redhat.com Scott Berens
            sberens@redhat.com Scott Berens
            Jorge Padilla, Joshua Packer, Joydeep Banerjee
            Joydeep Banerjee Joydeep Banerjee
            Scott Berens Scott Berens
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: