As a program, we have been focusing on scoping. An area to explore is whether we can support in identification of new work. We could build an agent to see based on the various engagements related to one client whether is a gap in the workstreams. ...

It would be nice to be able to clone or duplicate the workspace if it's not set up correctly. By duplicating or cloning, we should be able to edit what we need to do. An example is a workspace is set up but Jira is not selected.

Just learning so if this is already in play just disregard. It would be great especially for those of us migrating to Concourse / RAID log feature to be able to upload an existing Excel spreadsheet into RAID.

Ability to easily convert an existing question from one question type to save time on survey creation. For example if I started with a Drop down question type that and want to change to a Multiple Choice question type, I need to recreate the quest...

Put Simply: To ensure consistency, standardization, and proper setup of delivery projects, Jira workspaces should not be created directly within Jira. Instead, all new projects must originate through the Concourse scoping and activation flow, wher...

Put Simply: Currently, users must manually copy and paste a Salesforce Opportunity ID into Concourse to connect sales data to the scoping process. This feature would allow users to search and select Salesforce opportunities by name or ID , making ...

Concourse statuses are either (1) in progress or (2) completed. A Concourse moves to completed status when the associated Save It is closed out. On the landing page, could we categorize Concourse's into these two statuses and provide a definition ...

All QRG's for e-pro are linked to google drive and not accessible

Can we add the ability to attach existing files in the workspace? I have tasks/deliverables that use the same files as attachments. Currently I need to upload the same file again and again for different tasks. This creates a lot of duplicate files...

As a user I want the ability to answer a survey multiple times and submit unique entries (i.e., do not replace existing data). The use case is to use the surveys as a means to conduct interviews with key stakeholders in a standardized fashion.