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

The SLA is not working?

kalvarez May 28, 2024

The SLA is not working. I have already configured it, but the time to first response and time to resolution are not showing up in the queue. SLA.png

2 answers

1 vote
Gizem Gökçe _OBSS_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 28, 2024

Hello @kalvarez ,

Jira's own SLA counters do not work backwards. Whenever an SLA is enabled, it starts calculating for issues that are within the SLA counter limits at that time. It does not calculate for issues whose SLA definition endpoint has been reached. If you want to see historical SLA breaches, you will need to extract data from the Issue History. 

Lets say you set your SLA's when your issue is in In Progress status. This means that the Time to First Response counter will not be effective for this issue because the first response has already been given. 

I am not sure, but this may be the cause of your problem.

1 vote
Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 28, 2024

What does your SLA looks like? Are you filtering based on issue types of request types? If you use the same query in a filter will it include the request  that you are expecting the SLAs to pick up? What status is the request in?

kalvarez May 29, 2024

I copy the queue board with the tickets, one in progress and one to be done, as well as the SLA configuration....image.pngimage.png

Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 29, 2024

The only thing missing from your screenshots of the SLAs are the start and stop conditions, but as @Gizem Gökçe _OBSS_ mentioned above SLAs do not go back in time to start the SLAs for an issue.

Did you set up these SLAs after the requests included in your screen shots were created? Or was the SLAs already there before? If they were created before the requests, what priorities are on the requests? If so, what does the conditions look like for your SLAs?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events