Import and export
Load and update records in bulk from a spreadsheet, and export them in the same format to edit and re-import. Everything is on the Import / export page (editors).
How an import runs
- Choose what to import and an .xlsx (first sheet) or .csv file, up to 350 KB and 5,000 rows. Row 1 holds the column names.
- Run the dry run: every row is checked and shown as New, Updated, Unchanged or Error, and nothing is saved.
- Fix any errors, then import. Rows with errors are skipped and listed; the rest are saved.
Rows are matched to existing records (see each type's match key): a match updates the record, otherwise a new one is created. Blank cells leave values unchanged, and unknown columns are ignored.
Load order
Records refer to each other by name, so import in this order: vendors → software → capabilities → applications.
Applications
Matched by name. New applications are created in Assets too, so they take a little longer.
| Column | Value |
|---|---|
name | Required. Application name. |
description | Free text. |
lifecycle_status | A lifecycle status as in Assets, e.g. Active, Pending, Archived. |
criticality | Tier: 1, 2, 3 or 4 (1 = most critical). |
in_service_date, out_of_service_date | YYYY-MM-DD. |
vendor, product, product_version | Vendor name; software name and version from that vendor. |
licence_model, licence_entity | Licence model name (e.g. Subscription); licensed entity. |
business_owner | A person (see below). Replaces the current Business Owner(s). |
other_stakeholders | Role: person pairs separated by ;, e.g. Technology Owner: kim@example.com. |
capabilities | Capability codes or names separated by ;. Replaces the application's links. |
business_services | Business service names separated by ;. Replaces the links. |
documents | Links (https://…) separated by ;. Replaces the list. |
People
Write a person as an email address, an Atlassian account ID, or Name <email or account ID> (the form exports use). Only the part in angle brackets is used, so the name is just for readability. Emails are looked up in Jira as you; if Jira hides someone's email, use their account ID.
Capabilities
Matched by code, or by name when there's no code. Columns: code, name (required), description, criticality (tier 1–4), parent_code or parent_name, and owner (a person). List parents before their children.
Vendors
Matched by name. Columns: name (required), description, website_url, notes. Vendors from the end-of-life catalogue are read only.
Vendor software
Matched by vendor, name and version. Columns: vendor and name (required), version, description, software_type (A = application, T = tech stack), deployment_type (SaaS, On-Premise or Hybrid), category, and dates release_date, primary_support_end_date, extended_support_end_date, sustaining_support_end_date.
Export
Export any of these, plus the obsolescence report, as .xlsx or .csv. Exports use the import columns, so you can edit and re-import. Only records maintained on your site are exported (not the end-of-life catalogue).