Concourse & Jira DC Portal

🔹 Put Simply

Redesign the Admin Portal’s Assets Library so content owners can view, curate, and assign enterprise assets into PDM. The page will serve as a central record of all approved assets, whether manually created or ingested from external systems.

🔹 Why It Matters

• 📚 This page acts as the authoritative library for curating reusable assets into PDM work items. Without it, content owners can’t efficiently manage or assign relevant resources.

• 🔌 It must support both manual entry and automated ingestion via APIs from systems like Connected Source, Digital Lab, and Integration Nexus—offering a future-ready interface.

• 🔍 The UI must surface asset metadata (name, type, source system, work item associations) to allow precise filtering and tagging.

• 🔁 Assets inherit attributes from the work items they’re linked to, so metadata integrity and display are essential.

• 🧠 A clear, performant view of assets sets the stage for recommendation engines, curated tagging flows, and better planning experiences across PDM.

🔹 High-Level Acceptance Criteria

1. Asset Table View with Key Metadata

   • Given I access the Admin Portal Assets page,
     When the page loads,
     Then I should see a table of all assets with the following fields:

     • Asset Name

     • Source System

     • Type

     • Description

     • Work Item Association Count

2. Search and Filter by Metadata

   • Given there are hundreds or thousands of assets,
     When I apply filters (e.g., source system, asset type) or search by keyword,
     Then the results should update dynamically in under 300ms.

3. Scalability for Large Data Sets

   • Given the system contains a large volume of assets (e.g., >2,000),
     When the page is accessed,
     Then it should load in under 2.5 seconds and support virtual scrolling or pagination.

4. Support for Manual and API-Created Assets

   • Given an asset is created manually or via system integration,
     When it is shown in the list,
     Then its metadata should be consistently structured and equally editable/viewable.

5. Display of Inherited Attributes

   • Given an asset is linked to one or more PDM work items,
     When I view the asset record,
     Then it should display inherited metadata (e.g., Offering, Delivery Type) from its associations.

6. Tagging Assets to Work Items

   • Given I am curating a template work item in Admin Portal,
     When I browse or search the asset library,
     Then I should be able to select and tag one or more assets based on relevance and matching metadata.