I need to develop a new report that calculates ticket age for tickets opened with our helpdesk. Currently we calculate the age of the ticket by simply calculating the time between the OPEN activity and the CLOSE activity for the ticket.
We need a new report because we have multiple resolver groups, and the tickets sometimes get passed back and forth between groups until the correct resolver group is identified. So even though a ticket may have been open for a week, the proper resolver group may have only had the ticket for 1 day. This is further complicated by the fact the tickets may be reassigned to the same group multiple times during their life.
To solve this I am trying to build a report that calculates total time each resolver group held the ticket during the ticket’s life. There is a reassignment activity that I can use for the calculations. I need help figuring out how to properly organize the data and the calculation order.
When I pull the reassignment activities from the database I have the following:
NUMBERPRGN TYPE CST_DateStamp FromGroup ToGroup
IM1533774 Reassignment 5/19/2008 3:13:30 PM HD LEVEL 2 CRN TRIAGE
IM1533774 Reassignment 5/19/2008 5:14:24 PM CRN TRIAGE CRN MFI
IM1533774 Reassignment 5/20/2008 5:30:36 AM CRN MFI CRN SIEBEL
Where NUMBERPRGN is the ticket number, and the CST_DateStamp represents the time the ticket was reassigned from the FROMGROUP to the TOGROUP.
In order to calculate total time for each resolver group I need to calculate the time the group held the ticket before reassigning to the next group. The DATESTAMP of the reassignment is the ending time for the current FROMGROUP and the beginning time for the new TOGROUP.
I can subtract the first reassignment time from the ticket’s open time to get the length of time the initial resolver group had the ticket, but don’t know how to calculate the time from that first reassignment to the next and so on. Somehow the DATESTAMP of the first reassignment must be recognized as the start time for the second resolver group and the next reassignment DATESTAMP would be the closing time for the second resolver group and the starting time for the third resolver group.
I don’t understand how to make that happen, and make sure that the calculations are being done in the proper order – i.e. all reassignment times and groups have been pulled from the DB before the time calculations begin.
Any and all help is appreciated! If you need more info than this, please let me know.
We need a new report because we have multiple resolver groups, and the tickets sometimes get passed back and forth between groups until the correct resolver group is identified. So even though a ticket may have been open for a week, the proper resolver group may have only had the ticket for 1 day. This is further complicated by the fact the tickets may be reassigned to the same group multiple times during their life.
To solve this I am trying to build a report that calculates total time each resolver group held the ticket during the ticket’s life. There is a reassignment activity that I can use for the calculations. I need help figuring out how to properly organize the data and the calculation order.
When I pull the reassignment activities from the database I have the following:
NUMBERPRGN TYPE CST_DateStamp FromGroup ToGroup
IM1533774 Reassignment 5/19/2008 3:13:30 PM HD LEVEL 2 CRN TRIAGE
IM1533774 Reassignment 5/19/2008 5:14:24 PM CRN TRIAGE CRN MFI
IM1533774 Reassignment 5/20/2008 5:30:36 AM CRN MFI CRN SIEBEL
Where NUMBERPRGN is the ticket number, and the CST_DateStamp represents the time the ticket was reassigned from the FROMGROUP to the TOGROUP.
In order to calculate total time for each resolver group I need to calculate the time the group held the ticket before reassigning to the next group. The DATESTAMP of the reassignment is the ending time for the current FROMGROUP and the beginning time for the new TOGROUP.
I can subtract the first reassignment time from the ticket’s open time to get the length of time the initial resolver group had the ticket, but don’t know how to calculate the time from that first reassignment to the next and so on. Somehow the DATESTAMP of the first reassignment must be recognized as the start time for the second resolver group and the next reassignment DATESTAMP would be the closing time for the second resolver group and the starting time for the third resolver group.
I don’t understand how to make that happen, and make sure that the calculations are being done in the proper order – i.e. all reassignment times and groups have been pulled from the DB before the time calculations begin.
Any and all help is appreciated! If you need more info than this, please let me know.