At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Selected Draft terms | Select Submit for Review | Eligible terms move to In Review | Only draft terms can be submitted |
| Selected In Review terms | Select Approve Selected | Eligible terms become Approved | Creator, editor, or submitter cannot approve the same term |
| Selected Approved terms | Select Deprecate Selected | Eligible terms become Deprecated | Only approved terms can be deprecated |
| Selected non-approved terms | Select Delete Selected | Eligible terms are removed after a deletion version is written | Approved terms must be deprecated first |
| Up to 100 term IDs and one reason | Select Confirm | Success count and per-term errors | Each term is processed separately |
How it works
- Open Compliance Glossary for Confluence.
- Choose Draft, In Review, Approved, or Deprecated under All Statuses.
- Select individual terms or use Select all.
- Choose the available bulk action.
- Enter the required reason.
- Select Confirm.
- Review the completed count and every skipped record.
- Select Dismiss after recording the result.
Example
A reviewer selects 60 terms in In Review and chooses Approve Selected. Fifty-six pass the state and four-eyes checks. Four were created, edited, or submitted by that reviewer. Those four remain unchanged and appear in the skipped errors.
What this does not mean
Bulk management changes status or deletes records. It does not edit names, definitions, owners, dates, or synonyms in one action. A batch is not atomic across all selected terms. Some terms can succeed while others fail. Every operation is capped at 100 terms and requires an active license and administrator access.
Related questions
Next step
Filter by status, select a bounded group, and review every skipped result.
View on Atlassian Marketplace