Concourse & Jira DC Portal

Put Simply:

In PDM common deliverables will be used across practices/Offerings but have their require unique assets to the Offering in scope (specifically PM and QM deliverables). Assets should be associated to Offerings (Offering Details in Admin Portal) and only the assets that match the Offerings in scope should be included shown in scoping and the delivery plan for execution.

Why it Matters:

• To prevent having to add unique L5/L6s by practice or offering to help refine the assets, we would need to add an Offering detail tag to an asset and filter out based on offering selection.

• Ensure only relevant assets are made available to the project teams

• Enable content team to run bulk update bot on assets to add Offering associations and enable Asset filtering prior to Admin Portal 2.0 build is completed.

What's Needed:

• Offerings Detail attribute added to Asset schema

• APIs created to manage and read Offering Detail attribute associations to Assets

• Asset filtering logic in Scoping and Scope activation to only show Assets whose attributes match the selected Offering(s)

Not in Scope:

• Automatic inherit logic to add Offering Details to Assets when an asset is added to a work item