/build/static/layout/Breadcrumb_cap_w.png

Unassigned tickets

Hello all.
Ive been tasked with setting our KACE system up and over past 4 days have learnt a lot.
All seems to be ok, user interface is as we want it, but when a user logs a call it is automatically "unassigned" when i log i am unable to re-assign the tickets to anybody, there are 0 users to select.

Anybody have any ideas as to what i have not setup?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: GillySpy 12 years ago
7th Degree Black Belt
0
You must have at least a couple of users in your system since you cannot sign in without them but:
  • do users create themselves upon sign in (via ldap authentication) OR have you imported a bunch of users ahead of time. You should schedule an import nightly if using LDAP and do a one-time import to get started
  • do you have a label which represents the group of users that can sign in? OR do you have the queues set to allow all users as submitters?
  • do you have a label which represents the group of owners?
  • Are the labels above LDAP -based labels or manual ones? If LDAP then you must have them sign in to be populated OR follow this FAQ (http://www.kace.com/support/kb/index.php?action=artikel&cat=7&id=1094&artlang=en)
Posted by: dave1kelsey 12 years ago
Orange Belt
0
Thanks i have now solved this.
I'd managed to miss about the section of applying the "default ticket owners" label to the necessary staff!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

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