Concourse & Jira DC Portal

After meeting with and discussing about the concourse journey with various engagement teams both in India ACs and US, I have understood that managing a Concourse Workspace, especially when the project is either finally or temporarily, is a pain point and the same also creates confusions across teams.

I have noticed X points in this scenario -

• The project is completed but the Concourse Workspace created is not yet closed -

My idea - An automated email will be sent to any Workspace creator if there is no activity recorded in last 15 days in that workspace. After 3 such emails, if no activity is located or the workspace is not closed the workspace "status" would automatically be changed to "Parked".

• Introduce a new status "Park" -

Sometimes an engagement is temporarily closed but could / would become active in near future.

My idea - Introduce a new status "Park". If required, the Workspace creator would have the option to change the status of the Workspace as "Parked", so that if and when required the Workspace creator could again activate the Workspace.

If any "Parked" workspace is not Re-Activated within a certain period of time (may be 6 Months) An automated email will be sent to the Workspace creator enquiring the future plan for that workspace and after 3 such emails, if no activity is located or the workspace is not closed the workspace "status" would automatically be changed to "Closed".

This will give the Adoption Drivers a better clarity about the number of Parked Workspaces in every Platform / Practice / Sub-Practice