Concourse & Jira DC Portal


Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.


For immediate technical support, please follow this guidance to open a Service Now ticket.

Possible Beta Issue - ability to identify deliverables from primary vs component

When a component is added to an IS, the deliverables are merged within each Phase and not easily called out. For someone who is in Finance but added the Change Management (NextGenChange) component, they may not know which deliverables are form which map off hand but there is a need to differentiate. Currently, when you click on a deliverable and the right panel opens, you can see at the top which model it came from. However, in the Beta version you cannot. When the Beta version goes live unsure if this functionality will be lost (see attached pics). Either way, clicking on each deliverable to see the DM is tedious. Would be great if there was a way to auto-populate the NextGen Change deliverables to a "Change Management" workstream where of course users can still edit and rename/change. This would be the same for the Security & Controls component or others. Components are almost always a "workstream" or "team" so would make sense to tie those versus the end to end IS model should still be blank for user to populate.

  • Guest
  • Mar 16 2022
  • Closed
  • Admin
    Ritu Raj Agrawal commented
    8 Oct 03:14am

    This Idea is in relation to our native PMO pages in Concourse which we are no longer supporting. We are currently working on a migration plan for teams with active projects to move to Jira Cloud. Please be on the lookout for the migration communications so you can use the Delivery features found in Jira Cloud.