Time to First Response SLA not working properly

[Ahmed Hilal]

I'm working as Jira administrator in my company, and we faced a problem after setting up a new holiday.

The problem is related mainly to "Time to first response" SLA, as it most of the time breach although the responsible teams act rapidly to all tickets -sometimes within 10 minutes-.

We tried to make a re-index for the affected projects, update the calendar and refresh the SLA, but we didn't succeed in fixing the problem. 

Please let me know if there is any solution for this problem that we can try.

[Vitaly_Berezovsky_SaaSJet]

Hi @Ahmed Hilal 

You can try our addon SLA Time and Report for Jira.

Steps to set up Time to First Response on our addon:

Time to First Response
Choose the project you want to monitor, period, amount of days, and refresh intervals:

After filling in the fields, click the “Save” button. As a result, you’ll get:

I hope I've helped you!

The application has a 30-day trial period and is free for small teams (up to 10 users), so you can check how well it suits you. My team developed it so our support team can help you with the settings

[YY Brother]

Hi @Ahmed Hilal 

Welcome to our Community.

Could you please attach SLA configurations screenshots and a SLA breached ticket screenshot?

Thanks,

YY哥

[Ahmed Hilal]

Hi YY哥, 

[Ahmed Hilal]

Noted that, we've the SLA update icon all the time, that we can't handle or fix.

[YY Brother]

Hi @Ahmed Hilal 

Thanks for those screenshots. 

The Time to first respone of -12min means that this ticket is has exceeded the SLA target by 12 minutes (SAL breached). 

Please go to the 1st ticket MUSUP-812439 to verify it:

a）what priority it is;

b）what SLA target it is;

c）ticket created time;

d）ticket 1st response time;

e）calc the actual sla value = 1st response time - created time (excluding non-workin hours);

f）compare the actual sla value with "Time to first respone of -12min".

Thanks, 

YY哥

[Ahmed Hilal]

Hi YY哥, 

A) It's Low priority.

B) Time to first response should be within 2h

C) Created time:    23/Apr/24 9:44 AM

D) First response:  23/Apr/24 9:45 AM  [after just one minute].

[YY Brother]

I can’t figure out any reason. It might be related to this reminder:

”we've the SLA update icon all the time, that we can't handle or fix“.

Please raise a ticket to Atlassian Support.

Good luck!