Concourse Feedback
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.
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.
Hi Team,
Based on discussion with majority of stakeholders, PDM structure is quite complex and not allowing to do:
Staged or phased approach
Proper planning due to Child-> parent relations for PDM structure [it requires massive effort to managed
Idea is to simplify and reduce amount of elements pushed to Jira Cloud and allow users to customize L1-L3 accordingly to their needs.
Proposal [it will be great to test]:
Push to Jira Cloud only L4-L6 following the same order as in Concourse but without L1-L3.
Users can do the planning on their own and create L1-L3 e.g. as L1: Phase --> L2: PI --> L3: Sprint [etc.] [new work items can be created for it or we can even use current L1-L3]
Also, some ongoing activities [as managing governance] will not impact the planning and can be easily stored under relevant parent item.
Moreover, as previously raised L3 are not used by majority of teams as they have no assets assigned and only complicate the planning and management. It was previously raised under different Aha idea.
| Workspace Territory | N/A |
| Platform & Practice | CSX - CSX powered by Salesforce |
| Technology | Salesforce |
@Oleksandr Prokopiv Good to know! I've merged this idea with CONC-I-1820. We are still in discovery for that idea and will ensure I have discussions with PDM and Content teams regarding this functionality for only sending the L4-L6 work items for scope additions.
Hi @Emma Gattuso , you are right. Very often teams need to reorganize and restructure delivery plan. Such kind of simplified approach will allow teams to faster reshape PDM backlog.
Hey @Oleksandr Prokopiv - This goes hand-in-hand with our conversations around the need for Concourse to organize scopes into phases and releases, right? This is taking it a step further to say, "if the phase or release already has scope sent to Jira (the original scope), then for scope additions, only send the L4-L6 work items as the hierarchy structure is already built. Am I aligned there? Happy to chat further about this one too!
@Oleksandr Prokopiv I will raise your concerns written above with @Guest and @Kelly Hughes
Kelly / Team,
I do not agree that this topic should be closed, as variety of stakeholders raising this idea.
Could we please consider at least creating some simple jira Cloud Template [e.g. Salesforce Light] where only L4-L6 will be pushed to Jira?
Kind regards
Olek
Hi @Kyle Crawford ,
I appreciate your response. However, we have massive user complaints about lack of usability of 6 Level structure as it requires massive manual efforts to regroup and restructure.
One solution suggested in another Aha Idea: remove at least L3 from the PDM in general [as relation 1-2-1 between L3 and L4 have no value in planning and task assignment context and only complicates overall project plan].
Alternative solution, that we received from the users: to allow users repurpose L1-L3 accordingly to their needs as planning and assignment is mainly happens on L4 level.
The biggest complaint we are receiving: too many items to manage and lack of possibility to have smooth planning in place due to complex structure. It significantly slows down adoption as it causes increasing PMO efforts needed to maintain the project where PDM idea was to decrease the cost.
@Oleksandr Prokopiv
Thank you for the feedback. A core objective of PDM is to provide a consistent L1-L2 stage framework that is used throughout both the sales and delivery lifecycle, creating a common language for engagement teams and clients. Being able to clearly reference the current delivery stage is an important part of that approach.
While teams may have unique planning and reporting needs, those needs are intended to be supported through Jira tags, filters, and custom reporting rather than changes to the underlying PDM stage structure.
Hello @Oleksandr Prokopiv ! thank you for submitting this idea and the contributions you make to help us improve Concourse. The team will review your idea and come back to you shortly.