/build/static/layout/Breadcrumb_cap_w.png

K1000 7.0 device assignment and ticket submitter assets

Hi,

I'm playing with the new device assignment in K1000 7.0, but I am unable to link it to service desk tickets.
It is set to sync continuously and it works:

Device "MyLaptop" is assigned to me with the new device assignement. It shows also in the corresponding Asset.
Device "MyDesktop" is assigned to me with the new device assignement. It shows also in the corresponding Asset.

When creating a new ticket, setting me as the submitter, if I check the box to filter by assets attributed to the submitter, it shows nothing.

If I edit the "computer" asset type, create a new field named "User" and edit the asset "MyDesktop" to add myself in that field, then MyDesktop is available when creating a new ticket with me as submitter, but MyLaptop still isn't.

Is there a way to show assets belonging to the ticket submitter according to this new assignement feature?

Thanks for your help!

1 Comment   [ + ] Show comment
  • I've observed the same thing. Also, Computer assets that are "assigned to" a user aren't listed under the user details. I could add a separate field to the Computer asset for the assigned user, but this would be redundant. - brevidwa 7 years ago

Answers (1)

Answer Summary:
Posted by: rboitouzet 7 years ago
White Belt
2

Top Answer

Having no replies here I opened a ticket, turns out filtering assets by assignee in the service desk is planned and should be available in 7.1, if all goes well. Fingers crossed...

Comments:
  • Thanks, rboitouzet. Did they give a projected release date for 7.1? - brevidwa 7 years ago
    • Around April, they said. - rboitouzet 7 years ago
 
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