Concourse & Jira DC Portal

Put Simply: Automatically apply read-only restrictions and preserve data integrity across all integrated tools when a workspace is placed under legal hold.
Why it Matters: During legal or regulatory investigations, it's critical to preserve workspace data exactly as it existed at the moment of legal hold. Current manual processes are inconsistent and leave room for human error.
Additional Context:
Legal hold should act like a “freeze in time.” When enabled:

• All editing and deletion privileges must be revoked across Save It, Jira, Miro, Concourse, and other tools

• Comments, attachments, and versions must remain intact

• New versions can be created outside the legal hold scope, but originals must be untouched

• Ideally, a copy of the workspace or data snapshot should be archived in a restricted-access repository

• Most legal holds occur during engagements (not after), so normal delivery may need to continue in parallel

• Current Save It legal hold functions can be leveraged; Concourse and integrations must align accordingly

• Miro may require manual workarounds if native support is insufficient

• Jira has legal hold support; we need to automate triggering it via UC or similar process

Acceptance Criteria:

• Legal hold state clearly visible in Concourse UI

• Automatically sets all linked tools (Save It, Jira, Miro, etc.) to read-only or frozen

• Prevents user actions that modify or delete data, including comments and attachments

• Maintains audit trail and timestamps

• Option to archive current workspace copy externally for redundancy

• Legal hold on/off states should be synchronized across all tools

• Manual override or escalation path if needed