Time tracking
Hello everyone,
We're facing a time tracking problem with issues, whose type is Incident. The due date of the issues are let's just say after one week and the due date is set at the time of the status change but the issue still becomes breached and the "Time to next support step" displays as late issue:
When I edit issue and set Start date as today "Time to next support step" goes back to normal time trecking:
Have you any ideas how
2 answers
Hey, @Alexander Bondarev ,
Тhank you for your response. Sorry, I'm new to Jira so maybe I can't put information I have correctly.
"Due date" describes until when issue needs to be solved.
In most issues "Time to next support step" counts normally, f.e. issues below were created today. "Due date" is today and "Time to next support step" is also today, so the time frame is correct:
Although, in the example below "Time to next support step" counts time like this, even though due date didn't count down to an end (issue created on April 23rd). As you can see, the following "Due date" is 2021-04-28, the issue was created on April 23rd and where I marked on red ("Time to next support step") for some reason the SLA has been breached:
Ant then, because of negative time counting assignee gets this notification I showed before:
Any information regarding this subject will be appreciated and I'll look forward for your reply. If you require any additional information regarding this error I'll be more than happy to present it to you. Thank you very much in advance.
Hello,
I could really use some help here..
Also, some thing I noticed, that a few issues I checked has this difference:
On the left, time tracking of "Time to next support step" is correct, on the right - breached. Do you have any ideas?
Hello @Manon Soubies-Camy
Thank you for a reply. Here is the time to next support step calculation for most of our projects:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.