At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Structured CSV | Parse required and optional columns | Preview and validation result | File and row limits apply |
| Valid unique row | Create a governed term record | Imported term ready for workflow | Import is not approval |
| Duplicate or invalid row | Keep it out of accepted results | Row-specific error | The app does not silently merge conflicting meanings |
| Imported draft | Select Submit for Review | Normal review workflow | Four-eyes rules still apply |
How it works
- Open Terms.
- Select Import CSV.
- Choose the structured file.
- Review validation and duplicate results.
- Correct rejected rows and import accepted records.
- Submit the imported terms for review.
Example
A team imports 120 policy terms. Five rows have duplicate names and two have invalid lifecycle values. Those rows remain visible as errors. Accepted records enter the governed term workflow and still require review before approved use.
What this does not mean
CSV import accelerates record creation. It does not establish that a definition is correct, resolve conflicting source meanings, or approve terms. Teams remain responsible for source quality and review.
Related questions
Next step
Clean duplicates and assign reviewers before importing a large glossary.
View on Atlassian Marketplace