Jira Assets

[Maurice Adams]

When I try to search assets and look for historical data on who an asset belonged to and what JSM tickets were assigned to that item, I am not see this info.  Is this a feature of the Asset section of Jira?

[Martin Luethi _Mobility Stream_]

Hi @Maurice Adams 

As mentioned above, there is currently no native Asset history reporting in JSM Assets. On Jira Cloud, Asset history is tracked automatically. On Data Center, you may need to enable tracking. The built-in UI, however, only lets you view the history of one object at a time.

Since the history is stored, it can be extracted via the Assets REST API. While this works, it can be complex to implement and maintain.

If you need a more robust solution, especially for ongoing reporting, another option is to export your Assets and Jira history to a cloud data warehouse for analysis. This gives you complete flexibility, including the ability to reconstruct historical asset states and determine which assets were linked to issues at any point in time.

Our apps, Snowflake for Jira, Databricks for Jira, and Microsoft Fabric for Jira, export complete Asset history and Jira changelogs to make this straightforward.

We are also considering adding similar reporting capabilities directly to our Asset Manager for Jira app, which provides spreadsheet-style bulk management for Jira Assets.

Feel free to reach out if you would like to learn more.

Best regards,
Martin

[Arkadiusz Wroblewski]

Hello @Maurice Adams 

Just adding to @Anwesha Pan answer Assets can show you this, but only if the data was tracked in the right spo from the start.

To See history, open the object and check Activity > History. This shows changes if ownership was tracked as a specific attribute (like "Owner"). For JSM tickets, they have to be linked using a proper Assets custom field on the Jira side for them to pop up under the object's related work items.

If fields weren't actually being used at the time, Assets unfortunately can't retroactively piece that history back together for you.

That's kind of process which must be implemented from beginning to work.

Best,

Arkadiusz 🤠

[Maurice Adams]

I figured that is how to link the ticket to the asset was with something custom.  Thanks for confirming that info.  

[Petru Simion _Simitech Ltd__]

Hi @Maurice Adams,

For an individual asset, you can review the object's History tab in Assets to see attribute changes over time, such as ownership updates, provided those changes were tracked in the object attributes.

However, the native Assets interface is primarily designed for investigating one asset at a time. If you need to analyze historical information across many assets—for example:

• Find all assets owned by a specific user during a given period
• Review ownership changes across hundreds or thousands of assets
• Search historical attribute values in bulk
• Generate snapshots of asset data at specific points in time
• Export historical asset information for audits or reporting

then the native History view can become difficult to work with.

For organizations that need bulk historical analysis and reporting, Assets History & Snapshots Reporter for Jira (for Jira Cloud) provides additional capabilities for searching, reporting, snapshotting, comparing snapshots, and exporting historical Assets data across large numbers of objects.

So for a single asset, the built-in History tab is usually sufficient. For large-scale historical reporting, audits, or compliance requirements, a dedicated reporting solution may be worth considering.

Hope this helps.

Disclaimer: I am part of the team that developed and maintains Assets History & Snapshots Reporter for Jira Cloud.

Regards, 

Petru Simion

[Maurice Adams]

This looks like a good add on but it would be $125 a month vs using a totally different system, Snipe-IT at $40 a month.  It would be better if Jira Asset had the function of tracking the users and their assets in retro.  My boss, needs that feature so it is sadly going to make us resort to another solution.  Any insight on this happening soon or later down the road with Jira Assets in Atlassian?

[Petru Simion _Simitech Ltd__]

Hi Maurice,

Unfortunately I don't have visibility into Atlassian's roadmap, so I can't comment on whether this functionality will be added to Assets in the future.

At the moment, native Assets provides history at the individual object level, but does not provide bulk historical reporting, historical ownership searches across assets, point-in-time snapshots, or snapshot comparison capabilities.

For organizations that need those capabilities today for audit, compliance, or asset lifecycle analysis, they generally need either a dedicated reporting solution or a separate asset management platform.

Regards,

Petru

[Anwesha Pan]

Hi @Maurice Adams 👋🏻

First of all, welcome to community! ✨

To answer your question, Yes, this is an inherent feature of JSM Assets, though tracking past owners requires a specific setup. 

• Asset Ownership: To see who an asset currently belongs to or belonged to in the past, you must create a dedicated Owner attribute for your object type. If configured as an Object Reference pointing to a User/Identity object, the system will log an audit trail when the owner changes.
• Asset History: You can view timeline of attribute updates by opening the object within the Assets directory and clicking the History tab.
• JSM Ticket Assignment: Historical JSM tickets are not automatically listed within the asset's view unless an Assets Custom Field was used on the ticket. When a ticket links to an object, the association is visible natively within the ticket's history.

You can refer this article for more details on how to track assets in JSM.

I hope this helps & answers your question. 🙂

Thanks,
Anwesha

[Maurice Adams]

Thanks for the info!!!!