Concourse & Jira DC Portal

Let users create and assign workstreams, start and due dates, and owners on scoped work items in Concourse. Those values should carry into Jira Cloud (or the scope export) when the scope is activated.

Problem Statement
Today, workstreams, dates and owners can only be set after activation, in Jira, one item at a time. On large engagements this takes a lot of manual effort. For example, a team had to turn a scope of about 1,000 items into a working plan by hand. Teams often already know their workstreams, phase timing and owners from the SOW at the scoping stage, but they have nowhere to record them in Concourse. As a result, they redo the work after activation or build plans outside PDM.

Why It Matters

• Teams start earlier: planning begins during scoping instead of after activation.

• Less redundant effort: values are entered once and reused, not re-entered item by item.

• Fewer parallel plans: teams are less likely to keep separate spreadsheets or work breakdown structures.

• Cleaner handoff: values flow into Jira Cloud and into exports to client tools (see CONC-I-2572).

What’s Needed

• Workstreams: create engagement-specific workstream values within the scope and assign them to work items. Practice defaults from CONC-I-1823 could pre-fill these.

• Dates: add start and due dates to work items, set manually or applied in bulk to selected items, stages or phases.

• Owners: assign workspace team members as owners of work items.

• Sync at activation: map the values to Jira fields (Workstream, Start date, Due date, Assignee) and include them in the scope export.

• Optional fields: none of these should be required to activate a scope.

Like to Have

• Inheritance: child items inherit workstream, dates and owner from their parent, with the option to override.

• Bulk edit and filtering: support these in the Delivery Plan table.

Potentially Related Ideas
CONC-I-1823, CONC-I-1826, CONC-I-1905, CONC-I-1820, CONC-I-2508