Value Statement

Global search users expect parity for existing search features.

The following scenarios should use existing search details view:

• Resource is on global hub
• Resource is on managed hub
• Resource is on managed cluster managed directly by global hub.

The following scenario will need to launch out to the managed hub's search details view (so that it can use MCV)

• Resource is on managed cluster managed by a managed hub. (add launch icon)

*This is a future scenario not needed for TP

• Resource is in external data source, like Global Hub postgres, maestro, GRC Postgres, Kafka, etc.

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.