Summary

Add native support for the “four‑eye mechanism” in Jira Cloud so that certain critical actions (such as Project/Issue deletions etc) cannot be performed by a single user and always require approval from a second authorized user. 

Why This Matters

• Reduces risk of accidental data loss.

• Helps customers meet internal control / compliance requirements (four‑eye principle).

• Provides a clear audit trail that no single user can perform certain critical actions.

Alternatives: 

1. Permission‑based restriction

• • Issue deletion is controlled via the standard Delete issues permission.

• • Project deletion is restricted to Jira administrators (for company‑managed projects) and certain project admins (for team‑managed projects, depending on configuration).

• • Best practice is to limit these permissions to a very small, trusted admin group so that deletion is an exceptional, controlled action.

1. Soft delete and retention

• • Project deletion in Jira Cloud uses a soft‑delete / recycle‑bin pattern:

• • • Deleted projects are retained for a period (for example, 60 days) before permanent removal.

1. Monitoring & audit

• • Jira Cloud provides audit logs that capture administrative actions such as project and issue deletions.