Customer Description
The SLA clocks do not seem to work for tickets.
The clocks seem to be right for the new few tickets that are being logged in.
However, for most of the tickets, the sla time seems to be not working and appear blank.
Has anybody experienced such an issue and how could we possibly correct it?
Those ticket are created in April last Year. When have you implemented the SLA?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you open a new ticket with the same condition the SLA will be visible?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As you see in the above screenshot, one the newly created tickets have the response time. other tickets created around the same time have no SLAs. The customer domain is in a different query which follows the exact sequence as the one listed earlier.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
SUP-18125 is Severity 3 not 2 as you have defined in JQL for SLA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, you are right.
However, this customer domain is listed with Sev 3 on a different query which follows the same sequence as the one listed earlier.
And as you can see, only one of the many issues have their sla running and the others are blank.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If everything is set allright i think you may contact Atlassian Support.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Nidhi,
Could you upload a printscreen with the SLA conditions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We want our SLAs to start when the issue is created and pause every time we have set a comment to our customer.
However, many of the new tickets logged in have the SLAs as blank.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your SLA start when Issue is created and Stop when a Customer Commnet.
So if you have a couple o issues old that the SLA will not apply to them.
The SLA will work only for the new issues not for the old one( Open befor the SLA was implemente due the fact that you have the Start on Issue Created)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you please send me a full printscren of the conditions so I can see the JQL?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, I agree that SLAs would not work for the old issues.
However, even some of the new issues have blank SLAs.
Not sure what is wrong with the new tickets
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The new issues that are opened have Customer Domain != from the ones that are in JQL?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, the issues could be from any of the customer domain / customer name text field listed with the type being everything but improvement and of sev 2
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If the Ticket is:
Severity = 2
Type is different from Improvement
and Customer domain in the value list from above
It should work perfectly.
Can you please send a print screen o a issue that do not have SLA and meet all the conditions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.