Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-21616

Index additional fields from CMV CRs in Search (ACM 2.15)

XMLWordPrintable

    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • 0% To Do, 100% In Progress, 0% Done

      Feature Overview

      Final doc: https://docs.google.com/document/d/1bxMTpnehaEWjFcbRNHsC6EqQXuC8GeVfQ5FG15uw93c/edit?tab=t.0#heading=h.wnugfmy2tjk5

      Initial doc (VM)  https://docs.google.com/document/d/1OOTiB4fA8eg74w20Dcf8pIHWP1eCSd7gsQP6sgglZCI/edit?tab=t.0#heading=h.f09end8xoe4l 

      Initial doc (VMI)  https://docs.google.com/document/d/1OOTiB4fA8eg74w20Dcf8pIHWP1eCSd7gsQP6sgglZCI/edit?tab=t.0#heading=h.pe1cpct8cb9x

      Goals

      Users would like to see more information about their machines in tables and advance search.

      https://docs.google.com/document/d/1Dg-5kYkk3RDY_MPzGr0fyhm3uZUqonrhy52ruJnz5tU/edit?tab=t.0#heading=h.s99vcznvlpof

      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)?

        1. image-2025-06-18-16-28-24-281.png
          643 kB
          Matan Schatzman
        2. image-2025-06-18-16-28-51-541.png
          387 kB
          Matan Schatzman

              jpadilla@redhat.com Jorge Padilla
              showeimer Sho Weimer
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: