How do I see all of the objects assigned to a user (Assets)

[Ben Broster]

I'm currently trying to set up an asset registry for my organisation. 

The registry will store devices as objects (laptops, monitors, mobiles, etc) in different schemas and will assign them to users (based on profile ID). 

When I click on a user, it takes me to their profile, but none of their linked objects are visible. Is there a way to view to view all associated objects within the user profile?

Should I instead be storing users as their own object? Will I be able to link the User Objects to the User Profiles, and have that linkage remain for helpdesk tickets. Currently helpdesk is set up without an existing asset objects. 

Any advice would be appreciated. 

[Frederic Chartrand · Accepted solution]

Hi @Ben Broster 

If you look at a user profile, you will not see Assets objects related to them.

The way to do so is to create objects in Assets for each user. In the "User" object, you can link their JIRA user profile. And then, for each of your "hardware" object (laptops, mobiles, etc.) you must have an attribute called something like "Owner" and in this attribute, you store the "User object" you created, This way you'll be able to see each asset related to a certain user.

After that, if you want to pull each asset related to a user in a ticket let's say, you could create an automation rule that will pull the necessary information.

This page is a good starting point.

https://support.atlassian.com/jira-service-management-cloud/docs/insight-object-fields/ 

Of course, I simplify here but it's just to give you an overview of what's possible.

Bottom line, the only way to see all assets related to a user is to create an Assets object for each user.

Hope this helps

Have a nice day.

Frederic Chartrand

FMX Solutions - Gold Solution Partner

[Ben Broster]

Hi @Frederic Chartrand 

Thanks for pointing me in the right direction. I appreciate it!

[Derek White]

When pulling all the user's assets into a second custom field, the Assets system now links that object with the Jira ticket. So, all user's assets are "linked" to all Jira tickets for that user. This is incredibly unhelpful.

Other products, like Snap-IT, show other assets without incorrectly linking them to the issue.

This is a major problem that the only current workaround is to use AQL/Reports to find only the asset the ticket was reported against.

[florian.reichl_lovebyte.codes]

maybe our new plugin is going to help here:

https://marketplace.atlassian.com/apps/1235753/assets-owner-for-jira?hosting=cloud&tab=overview

we`re currently still working on some further core functionalities and therefor more than happy if you join our service desk and help us shape the product!