Jira Assets Custom Fields Missing From Excel Export

The symptom

You export an Assets object list to Excel or Google Sheets using Jira Service Management's built-in export, and the workbook comes back with the standard columns — object key, name, created date — filled in correctly, but every custom attribute you defined on that object type (serial number, owner, warranty date, whatever your schema tracks) is blank. The object clearly has the data, because it's visible in the Assets UI. It just doesn't make it into the export.

Why it happens

Assets (formerly Insight) is a separate data model layered on top of Jira Service Management, with its own API, its own attribute types, and its own query language (AQL). Jira's general-purpose Excel and Sheets export was built around issue fields — summary, status, assignee, standard and custom issue fields — and was never extended to walk an Assets object's attribute schema. When it's pointed at an Assets-backed screen, it exports what it knows how to export and leaves the rest blank. Atlassian documents this as a known limitation rather than treating it as a bug with a fix on the way, so it isn't something that resolves itself in a future Jira update.

What doesn't fix it

• Re-running the export with different column settings — the columns aren't being filtered out, they're never populated because the export path doesn't read the Assets attribute schema at all.
• Exporting from a saved AQL search instead of a plain object list — the underlying export mechanism is the same either way.
• Third-party tools that call Jira's general export API rather than the Assets REST API directly — they inherit the same gap, since the missing data was never in that API response to begin with.

What actually fixes it

The values exist and are readable through the Assets REST API, which returns each object's full attribute set, correctly typed, including custom attributes and references to other objects. Any export path that talks to that API directly, rather than going through the general Jira export, gets the real values. That's the entire fix: use the Assets API, not the issue-export API, and flatten the typed attribute values into workbook columns.

Don't have an Assets workspace at all?

If there's no Assets option in your site's navigation to begin with, the custom-field gap described here isn't your issue yet. See does Jira Service Management have asset management for the plan requirement that comes first.