Concourse & Jira DC Portal

I understand this is a limitation and would just need to live with this at this time. I wanted to share with you the scenario for future considerations.

I have reviewed this, but the guideline here isn’t practical for execution. As a PM, I would not want to do this since it breaks context and continuity specifically with JIRA and Google Drive, etc.

https://sites.google.com/pwc.com/concourse/work-with-concourse/use-save-it-for-document-retention/additional-guidance

More than often with clients, we are contracting for design only, and then another sow for implementation. Below is the screenshot of my workspace. We had initially contracted for Align only (hence the WS name “Global Align”) but client has agreed to continue to implementation. The reason I don’t want to create a new concourse workspace, since it internally will create a new JIRA workspace and a new google drive space. It’s a nightmare for execution teams to loose context to their previous work. The idea of a workspace to ensure continuity. Specially with JIRA, at the end of align there are open items, decisions, tickets that need to be resolved and roll right into the next phase. Creating a new JIRA space my teams will loose visibility or will need to work in two spaces, which is a overhead for them.

JIRA is client facing. Setting up a new JIRA workspace requires the client to transition as well, which is not ideal since its business continuity for them. SOW-2 in my screenshot is continuation of work from a client perspective. Thanks.

Lastly, setting up a new JIRA environment also has a cost impact on the engagement since we need to work with PMO Hub team to setup the new environment, copy over dashboards for the new workspace, and setup issue types and workflows.