I was wondering if one of you lovely people could help me with the following.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-comfficeffice" /><o></o>
<o></o>
To give a bit of background on what I'm doing, we have a ticketing system that we use to work on issues submitted by our user base. We will assign the ticket a severity and this will apply an SLA. For example a sev 4 may have an SLA of 48 hours. Occasionally we will stop the SLA clock while we gather further info, or change the severity and alter the SLA.<o></o>
When this happens, the SLA clock on the ticket isn't always accurate which makes it hard to work out when the SLA will breach.<o></o>
<o></o>
If the clock ticks 24/7 it's easy enough to work out how long is left. When the support hours are between certain times of the day it gets a bit trickier.<o></o>
<o> </o>
That text above only just makes sense to me so I’ll try and give an example:
<o> </o>
SLA is 48 hours total. Support hours are between 07:00 and 22:00, so the clock only ticks between these hours.
If an issue is logged at 08:00 on day 1 and is resolved on day 2 at 13:00, we took 20 hours of the SLA to fix the issue and so had 28 hours left on the clock.
That’s quite a basic example, as we might see the clock stop/start a few times between It being logged and resolved, but the principle is there.
I’m looking for a way to take the time and date stamps of when the ticket started, stopped etc, however many there are, and have excel calculate the time I have left on the clock.
Hope that makes sense to someone here and I’ll be very grateful for any help with this.
Many thanks
James
<o></o>
To give a bit of background on what I'm doing, we have a ticketing system that we use to work on issues submitted by our user base. We will assign the ticket a severity and this will apply an SLA. For example a sev 4 may have an SLA of 48 hours. Occasionally we will stop the SLA clock while we gather further info, or change the severity and alter the SLA.<o></o>
When this happens, the SLA clock on the ticket isn't always accurate which makes it hard to work out when the SLA will breach.<o></o>
<o></o>
If the clock ticks 24/7 it's easy enough to work out how long is left. When the support hours are between certain times of the day it gets a bit trickier.<o></o>
<o> </o>
That text above only just makes sense to me so I’ll try and give an example:
<o> </o>
SLA is 48 hours total. Support hours are between 07:00 and 22:00, so the clock only ticks between these hours.
If an issue is logged at 08:00 on day 1 and is resolved on day 2 at 13:00, we took 20 hours of the SLA to fix the issue and so had 28 hours left on the clock.
That’s quite a basic example, as we might see the clock stop/start a few times between It being logged and resolved, but the principle is there.
I’m looking for a way to take the time and date stamps of when the ticket started, stopped etc, however many there are, and have excel calculate the time I have left on the clock.
Hope that makes sense to someone here and I’ll be very grateful for any help with this.
Many thanks
James