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.
Put Simply:
Allow any Concourse Project Space to have many Salesforce Opportunity IDs associated to enable project extensions, change orders, phases, etc. to use the same integrated systems like Teams, Save It, Jira, throughout execution of longstanding projects.
Why It Matters:
Simplifies project lifecycle management: Each SF ID will get it's own scope, estimate, connection to Flex Budgets etc. but one Concourse Space will be used to orchestrate
What’s Needed:
UI updates: identification of SF IDs linked to the Project space.
Validation logic: Ensure linked opportunity IDs are only tied to one Activated Scope into a deliverable project plan (multiple draft scopes can exist for a single Opp ID)
Fallback: Continue supporting manual entry of IDs for edge cases.
Acceptance Criteria
Ability to merge multiple opportunities into a single Workspace, by allowing multiple SFIds to be included in a single workspace
Only accept related SF ids
Throw error message if SFIDs belong to different accounts
Questions
How to manage the Engagement lead/manager assignments if they are different for each opportunities?
To figure out how these SFids are tied to flex and epro
Garrett Kelchner
Allow reuse of SF ID's if workspaces created in error OR if workspace created is a test workspace
Merged