/build/static/layout/Breadcrumb_cap_w.png

Created By report

I have reports for Owners and Submitters but am looking to get one created for "Create By". Can't seem to find the field in the DB to report off of.


0 Comments   [ + ] Show comments

Answers (4)

Posted by: Hobbsy 1 year ago
Red Belt
0

You will probably find the ID of the tech who created the ticket in the HD_TICKET_CHANGE table, but you will need to join it to the user table in your SQL to get the name in your report.

Posted by: jjayko 1 year ago
Orange Belt
0

I was more looking to create a report with tickets created directly by end users as we have just opened up that ability. up until recently only techs were creating them

Posted by: Hobbsy 1 year ago
Red Belt
0

You may be able to find that out by excluding all the ID numbers for your techs, so run a report that says how many tickets were created that were not techs, would that work?

Posted by: Hobbsy 1 year ago
Red Belt
0

Try this SQL to get you going

SELECT HD_TICKET_CHANGE.HD_TICKET_ID, USER.USER_NAME, HD_TICKET.TITLE, HD_TICKET.CREATED

  FROM (ORG1.HD_TICKET_CHANGE HD_TICKET_CHANGE

        JOIN ORG1.HD_TICKET HD_TICKET

           ON (HD_TICKET_CHANGE.HD_TICKET_ID = HD_TICKET.ID))

       JOIN ORG1.USER USER ON (HD_TICKET_CHANGE.USER_ID = USER.ID)

 WHERE (USER.USER_NAME != 'Admin')AND(HD_TICKET_CHANGE.DESCRIPTION = "Ticket Created

")

You could expand it out by adding in OR statements to remove all your techs and even maybe use also filter the Created ticket field to reduce the reporting period

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