At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| New or edited term | Save a new governed version | Current term and prior version history | Only supported actions appear |
| Review decision | Record actor, time, state, and reason | Approval or rejection evidence | External reviewer qualifications remain organizational |
| Deprecation | Record a later lifecycle event | Visible deprecated state | It does not delete prior versions |
| Enterprise freeze | Copy the approved meaning and version | Release-bound term evidence | Only approved meanings enter the frozen snapshot |
How it works
- Open Terms.
- Select the governed term.
- Open its history view.
- Compare the selected version with its predecessor.
- Review actors, timestamps, states, and reasons.
- Use the required approved version in the controlled evidence package.
Example
The definition of “security incident” changes after a policy update. History shows the prior approved meaning, the edited fields, the submitter, the separate approver, and the reason. A baseline for the earlier release still preserves the earlier approved version.
What this does not mean
History records activity available to the app. It does not reconstruct decisions made only in email or another system. Teams should preserve external approval references where required.
Related questions
Next step
Review the exact approved version before relying on a term in release evidence.
View on Atlassian Marketplace