Concourse & Jira DC Portal

Epic 1292752: Admin Portal in Micro Frontend App (Post MVP)

🔹 Put Simply

Rebuild the Admin Portal using a micro-frontend (MFE) architecture to support modular development of core PDM curation functions—including Offering structure, Engagement Artifact hierarchy, and reusable delivery building blocks.

🔹 Why It Matters

• 🔧 The Admin Portal is the governance engine for reusable delivery content, but today it lacks scalability and flexibility.

• 🧱 Rebuilding in MFE allows us to independently develop and scale the pages and apps needed to support delivery teams, content owners, and global leadership.

• 🗂️ We need dedicated, performant UIs for managing Engagement Artifacts, Offerings, Building Blocks, and Tasks—all tied to the estimation models and metadata required by PDM.

• 🔍 These structures will form the backbone of PDM 2.0’s scoping, costing, and reuse workflows.

🔹 High-Level Acceptance Criteria (with Component Pages)

1. Engagement Artifact Hierarchy Page (Stage → L4 Artifact)

   • Given I open the Engagement Artifact page,
     When viewing the structure,
     Then I should see the full 4-level hierarchy defined by the Global Delivery Board:

     • Stage

     • Stage Group

     • Stage Block

     • L4 Engagement Artifact

   • Each level should support:

     • Inline editing of names and metadata

     • Hierarchical view with expand/collapse

     • Metadata tagging (e.g., Delivery Type, Approval Status)

2. Offerings Tree Management

   • Given I access the Offerings tree page,
     When viewing the structure,
     Then I should see:

     • The nested Offering hierarchy from the Commercial Office

     • The associated Product Code for each Offering, retrieved from an external system like Salesforce or GCVP

     • Standard functionality to add, rename, archive nodes and assign attributes

3. Offering Details Page (Lowest-Level Offering Editor)

   • Given I select a lowest-level Offering node,
     When I view its details,
     Then I should be able to:

     • Define Technology and Territory applicability

     • Attach L4 Engagement Artifacts and their Building Blocks

     • Manage team ownership and publishing status

4. Work Item Assignment to Offering Details

   • Given I manage an Offering Detail,
     When I link a work item,
     Then I should be able to:

     • Select from L4 Engagement Artifacts

     • Choose and configure Building Blocks tied to those artifacts

     • Ensure correct metadata inheritance (e.g., Estimation Model)

5. Task & Subtask Curation

   • Given I am editing an Offering Detail,
     When I create or update a Task or Subtask,
     Then I should be able to:

     • Define task name, type, tags, and notes

     • Share tasks across Offering Details using the same Estimation Model

     • Prevent editing of shared tasks unless explicitly unlinked

6. Building Block Listing + Artifact View

   • Given I navigate to the Building Blocks page,
     When I select a Block,
     Then I should see:

     • Associated L4 Engagement Artifacts

     • Editable metadata

     • Quick links to view or edit the relevant Engagement Artifact in context

7. Territory Configuration Page

   • Given I open the Territory Management page,
     When I view the list of ~90 territories,
     Then each row should display:

     • Country Name

     • Country Code

     • Onboarding Status (toggle)

     • Salesforce Data Access Approved (toggle)

   • Admins should be able to:

     • Filter by onboarding status

     • Search by name or code

     • Update toggles and save

8. Technology Management Page

   • Given I access the Enabling Technologies page,
     When the page loads,
     Then I should see a list of technologies sourced from Salesforce or GCVP

   • Each record should display:

     • Technology Name

     • Source System

     • Unique ID

   • Admins should be able to:

     • Search and filter

     • Manually create overrides (if source data is stale)

     • Tag technologies to Offering Details, assets, tasks, or subtasks