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 MarketplaceRequires Jira Service Management Premium or Enterprise. Assets is only available on those tiers, so on a Free or Standard site there is no Assets workspace for the app to read. You also need an account with Assets permission on at least one object schema, and at least one schema containing objects.
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.
Fixes the standard-export gap — includes all custom fields and attributes, not just standard fields.
Practical limits are Excel and browser memory, not an app-imposed cap.
See every change in a diff before anything writes to Assets.
Workbook generation and parsing happen in your browser inside Forge's Custom UI.
A round trip for Assets data: export to Excel, review or bulk-edit it there, then import the changes back — with a dry run before anything is written.
The app runs inside Jira as an Atlassian Forge app, so there is nothing to install locally and no separate login. It respects your existing Jira permissions.
Click Export to Excel. Unlike the standard Assets export, every attribute comes through intact — including the custom ones that normally get dropped — and there is no imposed row cap.
Bulk-edit in Excel, hand it to someone for review, or reconcile it against another system. The workbook is a normal styled .xlsx, not a fragile export format.
Click Import updates and map your columns. The dry run shows every change as a diff before anything is committed, so you approve the result rather than discovering it. Workbook generation and parsing both happen in your browser — object data never leaves Atlassian's context.
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.
No — practical limits are Excel and browser memory, not an app-imposed cap.
No — workbook generation and parsing both happen in your browser inside Forge's Custom UI. The data never leaves Atlassian's servers.