Connecting Assets to Organizations

[Bob Edgar]

Hello, I am a new user and am trying to set up my Demo with Assets. I have a pretty good idea of how to create assets and attributes. I am having a hard time setting up or connecting the assets with organizations. Our assets are the machines that we build and deliver to our customers at their various facilities (organizations). I am trying to set up the assets to be tied with an organization, similar how a custoemr is tied to an organization. This way if I am talking to a customer from Company X and working on an issue with one of their machines, I can tie the ticket to the machine so that everything is aligned under that organization. Also, this would prevent the agents from picking assets that do not belong to that company when creating or working on a ticket.

Just wondering if this is possible and how I might be able to do it. 

Thanks!
Bob

[Marc -Devoteam-]

Hi @Bob Edgar 

Has each the object type for user/employee and attribute based on type user, to link it with the actual Atlassian user?

Then based on the reporter, you could show all related assets in a singe field or mutliple custom field based on an asset.

[Alex Koxaras -Relational-]

Hi @Bob Edgar 

Organizations in Jira is a total different entity from assets. That's why these two are not connected out of the box.

What you can do is to create a new object type called Organization. On this object type make your connections to the other various object types (machines etc) based on your customers. Then create a new asset custom field named "Organizations Assets" (or similar) and populate it with a post function.

Does the above cover your need, or you need your customer to be able to pick e.g. from assets that belong to them (based on the relationships you have setup on assets)? 

[Bob Edgar]

Thanks Alex,

I think that will get me most of the way there, I appreciate the response. To your last point, it would be helpful if when a customer is creating a request or a ticket, if they could see their assets and pick from it when they know which it is. It would not be manditory for them to pick it, but if they could see only their assets and pick from them, that I think would be ideal. Also, the agents when working a ticket, if they could see just the assets related to the custoemr they are working with, that would be good as well.

For example if "Joe Jones" (joe.jones@doesnotexist.com) is logged in to the portal and creating a ticket, it would see that Joe Jones is linked to "Does Not Exist" company and would offer their (x) number of machines (assets) to chose from. Then when my agent gets the ticket, he would already know what machine (asset) that Joe was inquiring about. In the case where Joe did not pick the machine, my agent could add it (or change it) later in the ticket.

Thanks
Bob