Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,332
Community Members
 
Community Events
176
Community Groups

SLA clock (Response and Time to resolution) does not work

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?

 

2 answers

0 votes

Those ticket are created in April last Year. When have you implemented the SLA?

Yes, the SLAs were already implemented by then. 

If you open a new ticket with the same condition the SLA will be visible?

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.

SUP-18125 is Severity 3 not 2 as you have defined in JQL for SLA.

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. 

If everything is set allright i think you may contact Atlassian Support.

Alright. Thanks. 

0 votes

HI Nidhi,

 

Could you upload a printscreen with the SLA conditions?

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. 

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)

Can you please send me a full printscren of the conditions so I can see the JQL?

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 

The new issues that are opened have Customer Domain != from the ones that are in JQL?

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

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?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events