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.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
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.