Scripting Question


01/26/2017 1192 views
Can anyone tell me what is the difference between the CREATED and the TIME_OPENED fields on Kace K1000
0 Comments   [ + ] Show comments


All Answers

The TIME_OPENED, TIME_CLOSED, and TIME_STALLED columns are related to ticket status states. A status can have a state of either stalled, opened or closed. The default New status has a state of Stalled, so when a ticket is initially created it will be in a stalled state and the TIME_STALLED column will be set to that time (which should match the CREATED timestamp). Once the ticket's status is set to an Opened state the TIME_OPENED column will be set.

So, the difference between the CREATED and TIME_OPENED columns will show you how long it took from the time a ticket was created until it was changed to a status with the Opened state.

These columns are updated whenever the status changes between states, however, so the difference between CREATED and TIME_OPENED is not necessarily how long it took for the first status change to occur. For instance, if a ticket is stalled at 8:00am, then opened at 8:30am, then stalled at 8:35am, then opened at 9:00am, the TIME_OPENED column will reflect the 9:00am change and the TIME_STALLED column will reflect the 8:35am change.

Does that answer your question?

Answered 01/26/2017 by: chucksteel
Red Belt

  • Thanks Chuck
    • Chuck, i'm trying to create a report that gives me tickets w/ an opened status of > 30 days and the system is not cooperating. what am i doing wrong? - Mo
      • Not sure. I suggest you create a new question and include your current query.

Don't be a Stranger!

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

Sign up! or login

View more:


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