Policy Lifecycle

A Candidate is the revision under review. Active is the revision selected by the current immutable enforcement release. Saving, testing, replacing, or restoring a Candidate never changes Active enforcement.

Use Restore as candidate to copy supported historical content into a new Candidate; history is not overwritten. Publish verifies a complete desired set across both policy families, stages an immutable release, checks the expression cache and snapshot, and switches the Active pointer only when readback is conclusive. A failed or ambiguous publish leaves the last-confirmed release authoritative until reconciliation proves otherwise.

Only Jira administrators can view policy history, technical release details, or publishing controls.