Why Jira Assets Reference Attributes Export as Internal IDs Instead of Names

The symptom

A reference attribute in Assets is one object pointing at another: a server pointing at the datacenter it's racked in, a license pointing at the software it covers, a laptop pointing at the employee it's assigned to. When that attribute comes out of an export, some tools render it as a long internal object ID rather than the object's actual key or name, so the column is technically populated but tells the reader nothing without going back into Assets to look each ID up.

Why it happens

A reference attribute's stored value is a pointer: an internal identifier for the object on the other end, not the label you'd recognize. An export path that reads the attribute value and writes it straight to a cell, without a second lookup to resolve that identifier into the target object's key or name, produces exactly this: a column of correct but unreadable IDs. It's not corrupted data, and it's not a bug in Assets itself. It's an export that stopped one step short of finishing the job.

Why this is worse than a blank column

A blank column is obviously wrong; someone notices and asks why. A column full of ID-looking values looks like it worked. It passes a glance-over, gets used in a report or an audit, and the mistake only surfaces later when someone tries to click through or manually cross-reference an ID and can't make sense of it. A workbook that's technically complete but practically unreadable is a worse failure mode than one that's honestly incomplete.

What the fix actually requires

1. Read the reference attribute's value to get the target object's internal identifier.
2. Look that identifier up against the Assets API to retrieve the target object's own key and label.
3. Write the readable key or label to the export, not the identifier that pointed at it.
4. Confirm this on a reference attribute where you know the expected target, not just any populated cell, since a correct-looking but wrong reference silently breaks the same way a raw ID does.

A related but different gap

Reference attributes exporting as IDs is a different failure from custom attributes not exporting at all. See why Jira Assets custom fields are missing from the standard Excel export for that one.