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?
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 🤠
I figured that is how to link the ticket to the asset was with something custom. Thanks for confirming that info.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You can refer this article for more details on how to track assets in JSM.
I hope this helps & answers your question. 🙂
Thanks,
Anwesha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.