/build/static/layout/Breadcrumb_cap_w.png

Assigning asset to ticket

Hi, 

I am having trouble finding/figuring out how to assign an asset to the ticket based off who the submitter is.

Does anyone have any help they can provide with this?
Thanks!


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Hobbsy 5 years ago
Red Belt
1

If we are talking device assets then you will need to have the ownership settings set in the SMA options to assign ownership.


On logging a ticket if you go to the Device field and tick the "filter on submitter assigned devices" option you should only see the submitter's owned devices in the dropdown.


If you are talking about any Asset type then there is a bit more work to do. For an Assert to show ownership, within the Asset type you will need to add in an owner field. Once the owner field has a value in it i.e. a user from your LDAP import then the ownership of the asset is assigned. 

Owned assets can be found in the user record at the bottom of the screen.

As with Devices, on logging a ticket if you go to the Asset field and tick the "filter on submitter assigned devices" option you should only see the submitter's owned Assets in the dropdown.


Comments:
  • Ive got both devices and assests auto assigning to users, but when i check the "Filter on submitter assigned assets" it gives a result of 0 - khoelle 5 years ago
    • So when you say that you have "Assets Autoassigning to users" what exactly do you mean? - Hobbsy 5 years ago
      • It is set up so that "assets" match "devices" by BIOS name(service tag) so that the "assigned to" in the asset detail is the logged in user. But when we goto a ticket for one of those users it shows 0 when I try and "filter on submitter assigned assets" - khoelle 5 years ago
      • If you are referring to the Assigned User field about 3 lines down in the inventory then that is still the Device ownership. You need to add a user type field to your Device Asset Type and that will assign the asset to an owner. If you would like a quick webex to go through an set everything correctly then I would be happy to help? - Hobbsy 5 years ago
      • I guess I am confused as both the device and asset have the same "assigned to" user - khoelle 5 years ago
      • Yep you can thank KACE for introducing that confusion.....Mr G are you reading this?? I would just need 15 mins to explain the Device/Asset Relationship, how it works and how you use it to get the results you need. Anytime, just let me know and we can set up a call - Hobbsy 5 years ago
      • That would be great! Do you have a time in mind? - khoelle 5 years ago
  • So I finally understood a bit of what you were saying and added the "owner" field in the asset table, but now I am stuck on how to have owner=assigned to. manually setting it does work for tickets now. - khoelle 5 years ago
    • And there is the issue, the asset area of the SMA is very much a manual place to update data, unless you are using apps like the Go app or our BarKode App. The only other way you could automate would be to create a ticket rule to synchronises the fields but that is only applicable to device assets, any other type of asset would have to be updated manually to show ownership - Hobbsy 5 years ago
      • Do you happen to know where custom fields are in sql for assets? I cant seem to find my new Owner field in the tables and its giving me a headache. probably going to put it aside for today. - khoelle 5 years ago
      • Please please please just email me on the account in my profile to setup a call, you just need the right training to help you understand - Hobbsy 5 years ago
Posted by: thespineffect 5 years ago
White Belt
1

Can I get some help with this also. I don't think I added the owner field properly and I do not know how to add the asset to it manually.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ