Create Automated Non Test concourse workspace closure process after 30 days of inactivity
RIght now only test workspaces have a 30 triggers that launches to close it, we need a similar trigger for non- test workspaces. This would allow to close pursuit workspace that were not Won" or did not move to delivery so we save cost associated with jira cloud licenses.
After further review, there will be implementation of automated closure activities but they will be based off of a combination of Concourse and Save It inactivity/closure. Engagement teams are still expected to keep their workspace up to date and take action to close Concourse workspace and Save It based on firm guidance but this will be a back up solution. This is targeted for the FY27Q2.
Please can you share reasoning and the forum where this was reviewed/decision was made? If there is no-tech based prompt the requirement for financial impact guidance and license management needs to be met through guidance and central communications.
Hi Priya and Rose, we will not be implementing an automated process for closing non-test workspaces. Workspace Closure will be designed to allow the user to choose why they are closing a workspace and it would include if it was not won. There will be other efforts done for inactivity related to licenses and emails reminding users about older workspaces needing to be closed but workspace closure on a non-test/ non-demo site will be a requirement for the engagement team.
Would the workspace have been activated if it wasn't won? So would there be no cost incurred? I think we'd have to check about Safe Delivery/R&Q timelines if there were any extended review periods needed.
After further review, there will be implementation of automated closure activities but they will be based off of a combination of Concourse and Save It inactivity/closure. Engagement teams are still expected to keep their workspace up to date and take action to close Concourse workspace and Save It based on firm guidance but this will be a back up solution. This is targeted for the FY27Q2.
Please can you share reasoning and the forum where this was reviewed/decision was made? If there is no-tech based prompt the requirement for financial impact guidance and license management needs to be met through guidance and central communications.
Hi Priya and Rose, we will not be implementing an automated process for closing non-test workspaces. Workspace Closure will be designed to allow the user to choose why they are closing a workspace and it would include if it was not won. There will be other efforts done for inactivity related to licenses and emails reminding users about older workspaces needing to be closed but workspace closure on a non-test/ non-demo site will be a requirement for the engagement team.
relates a little to this one:https://concourse.ideas.aha.io/ideas/CONC-I-2518
Would the workspace have been activated if it wasn't won? So would there be no cost incurred? I think we'd have to check about Safe Delivery/R&Q timelines if there were any extended review periods needed.