Concourse & Jira DC Portal

Put Simply:

As delivery plans become more dynamic, users need flexible ways to visualize and manage scope content. A view organized by offerings helps users see and manage work items in the context of how services are sold, structured, and delivered.

Why It Matters:

• Aligns with user mental model: Scopes are built around offerings—users want to refine and manage work items the same way.

• Improves scoping clarity: Grouping by offering helps users easily see which work belongs to which part of the solution.

• Reduces friction: Especially helpful in cross-practice or multi-offering engagements where deliverables are spread across multiple services.

• Supports future personalization: This layout creates room for offering-specific logic, filters, or tagging in later releases.

What’s Needed:

• A toggle or option in the Delivery Plan UI to organize work items by Offerings.

• Each offering displays as a grouped section (card, panel, or expandable container).

• All deliverables and their child items (tasks, subtasks) appear nested within their assigned offering.

• Backend support to ensure each work item is correctly attributed to an offering, including offering detail mappings.

• Optional filters and quick actions to manage offerings individually (e.g., expand/collapse, deselect all).

• Maintain all interaction patterns (e.g., checkbox selection, hierarchy behavior) from other views.