AE

Assets Excel Sync for Jira Service Management

Jira's standard Excel and Sheets export silently drops Assets custom-field values. This Forge app exports any Assets object type to a no-row-cap, typed .xlsx and re-imports edits as validated bulk updates — all in your browser, so Assets data never leaves Atlassian.

Install from Atlassian Marketplace
Marketplace listing coming soon

What is Assets Excel Sync for Jira Service Management?

Assets Excel Sync for Jira Service Management is a Forge app published by Cody Labs. Jira's standard Excel and Sheets export path leaves Assets (formerly Insight) custom-field values empty — Atlassian documents this and tracks it as an open issue. This app talks to the separate Assets REST API directly, exports any object type's attributes to a typed, styled workbook with no artificial row cap, and supports a reviewed re-import: every change is shown in a dry-run diff before anything commits. All processing runs client-side inside Forge's Custom UI, as your user, so Assets data never leaves Atlassian's infrastructure. See the privacy policy for full details.

What it does

Every Assets attribute

Fixes the standard-export gap — includes all custom fields and attributes, not just standard fields.

No row cap

Practical limits are Excel and browser memory, not an app-imposed cap.

Dry run before commit

See every change in a diff before anything writes to Assets.

Zero data egress

Workbook generation and parsing happen in your browser inside Forge's Custom UI.

Pricing

Trial
$0
  • 30-day trial
  • Via Atlassian
  • Premium+ tier
Paid
~$1/user/mo
  • Volume tiers
  • Paid via Atlassian
  • JSM Assets premium

Frequently asked questions

Does Jira's normal export include Assets fields?

No — Atlassian's own standard Excel and Sheets export leaves Assets custom-field values blank. This app talks to the Assets API directly and exports every attribute.

Is there a row cap on export?

No — practical limits are Excel and browser memory, not an app-imposed cap.

Does Assets data leave Atlassian's infrastructure?

No — workbook generation and parsing both happen in your browser inside Forge's Custom UI. The data never leaves Atlassian's servers.