opensafely-core / job-server

A server for mediating jobs that can be run in an OpenSAFELY secure environment. q.v. job-runner
https://jobs.opensafely.org
Other
5 stars 11 forks source link

Align workspace status with project status #4279

Open LFISHER7 opened 6 months ago

LFISHER7 commented 6 months ago

I have recently marked this project as completed, following the project completion documentation. This doesn't include any details on updating the status of individual workspaces. The result is a project marked as Completed with workspaces in the project remaining Active.

Screenshot 2024-04-15 124741

I could archive the workspaces, but I don't know what that means in a practical sense.

It would be helpful to:

  1. Document what archiving a workspace means.
  2. Think about whether archiving workspaces should be included in the project completion workflow. Alternatively, add another status that can be used when a workspace is no longer being used
lucyb commented 6 months ago

Thanks for reporting this Louis, I agree it's not clear at the moment what happens when a workspace is archived (or even when it should be archived).

In practical terms, nothing really happens at the moment, except it can be used by the RAP Team as a trigger to archive the workspace on the secure backend.

This probably quite a bit of work to untangle and find a proper solution to, so I'm going to keep the ticket in our backlog, but we won't be able to do any work on it for the moment unless it starts to cause problems for anyone.

iaindillingham commented 4 months ago

I've just read this issue, as Catherine and I have been discussing projects, workspaces, and GitHub repositories. Thanks for reporting it, @LFISHER7 and for investigating further, @lucyb. It's really useful and interesting.