/build/static/layout/Breadcrumb_cap_w.png

Why would a ticket submitter's name display as "1" in KACE?

Would anyone be able to tell me as to why this ticker submitter is being displayed as 1 in KACE? I opened the ticket and it has the email of the person who submitted the ticket and the individual has submitted tickets before and it obviously displayed fine. When end users create a ticket it should auto-populate with their name in the submitter section. Anyone have any ideas?
bWCwuN.png

6 Comments   [ + ] Show comments
  • To further clarify... why was his name changed in KACE? It's a bit odd. - JZycho 7 years ago
  • Can you check the user record within KACE, how does that look? - Hobbsy 7 years ago
  • I looked at it and changed the Name field back to the users name. That was one of the first things I did, but why did it randomly change to 1 is my question. Like.. is it something that could potentially continue to pop up in the future that end users name change? Something along those lines. Or is this just some freak occurrence. - JZycho 7 years ago
  • If you have history enabled you can see when (and possibly by whom) the name was changed on the user details page. Are you importing users via LDAP? - JasonEgg 7 years ago
  • Can you check if you have custom ticket rules? If yes - work all of the custom ticket rules correct? - svmay 7 years ago
  • This happens when a user logs on for the first time but is not already imported into the system. The next scheduled LDAP sync should update the name. - kaluaabyss 7 years ago

Answers (0)

Be the first to answer this question

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