Resolved/Done issues sudden breaches after long time
Asked by Fuji:

Why does resolved / Done tickets suddenly breach within our perfectly normal working SLA?

Normally it functions good, but after 6-12 month, some of our old resolved issues comes up as breached on current day, and keeps staying on current day with time passing.

Last time this happen (6-12 month ago), I refreshed the tickets by opening and resolving issues again, but then current report will look like we finished much more than we actually did that sprint.  
But at least the breached tickets disappear. Its just annoying that this as happen several times, so now I want to find the root problem.  

I cannot see any pattern?  

Both Time to first Response and Time to Resolution have problems with old tickets suddenly breaching with thousands of hours.

<br />

**Our report (Pic. below)**

![Screenshot 2024-06-14 145647.png](https://community.atlassian.com/t5/image/serverpage/image-id/329916iAB82ADE2EF6D26C3/image-size/large?v=v2&px=999 "Screenshot 2024-06-14 145647.png")  

![Screenshot 2024-06-14 145844.png](https://community.atlassian.com/t5/image/serverpage/image-id/329917i0C00B7112728472B/image-size/large?v=v2&px=999 "Screenshot 2024-06-14 145844.png")

<br />

**An example of one of the breached issues that suddenly is breached on current day on the report, that has status resolved and resolution "Done" (pic. below)**

![Jira communicty billede.png](https://community.atlassian.com/t5/image/serverpage/image-id/330338i4B693871534A349A/image-size/large?v=v2&px=999 "Jira communicty billede.png")

<br />

<br />

**Our SLA - Time to Resolution (2 pics. below)**

![Screenshot 2024-06-14 151216.png](https://community.atlassian.com/t5/image/serverpage/image-id/329923i85C4B0C2A85E753B/image-size/large?v=v2&px=999 "Screenshot 2024-06-14 151216.png")

![Screenshot 2024-06-14 151226.png](https://community.atlassian.com/t5/image/serverpage/image-id/329924i01DEA4759D0136B2/image-size/large?v=v2&px=999 "Screenshot 2024-06-14 151226.png")

**Workflow (pic below)**   
![Screenshot 2024-06-14 150618.png](https://community.atlassian.com/t5/image/serverpage/image-id/329919i84F1903AD53BEE37/image-size/large?v=v2&px=999 "Screenshot 2024-06-14 150618.png")  

<br />

Kind regards,  
Fuji


Answers:
author: Ash Yadav
body: Hi [@Fuji](/t5/user/viewprofilepage/user-id/5280741)

The only thing I can't gauge from the data you've provided is whether or not the resolution has been set. That's one of the conditions for the SLA clock to stop it seems.

I've seen cases where users who designed custom workflows, missed setting the resolution on screen, and it results in "Resolved" issues with the resolution as "Unresolved"

KR,

Ash

comments: author: Fuji
body: Thank you for your answer.  

But if the result would be "Resolved" issues with the resolution as "unsolved", wouldn't it show on upper right side of the ticket (as shown in the 2. picture example up in the description\^\^)?  

Where do I see if I missed the resolution on screen?

If I look on screen, I can't seem to find it.  

![Sk?rmbillede 2024-06-18 124534.png](https://community.atlassian.com/t5/image/serverpage/image-id/330350i1A5B10375257709A/image-size/large?v=v2&px=999 "Sk?rmbillede 2024-06-18 124534.png")

It has not anything to do with post transitions?

![Sk?rmbillede 2024-06-18 130018.png](https://community.atlassian.com/t5/image/serverpage/image-id/330352iA7E12F4332AF279E/image-size/large?v=v2&px=999 "Sk?rmbillede 2024-06-18 130018.png")


author: Ash Yadav
body: Try using a JQL search to filter issues that are in "Resolved" or "Closed" status with a resolution of "unresolved".

This should at least show you if anything matches that theory, if it does, you have your answer if the issues that are breaching and both match the JQL appear.

BTW if you move to resolve an issue, are you presented with an option to choose a resolution?

KR,

Ash


author: Fuji
body: I try the filtering with status of closed and resolution. But could not find anything.  

<br />

CLOSED (below)

Some tickets came up, but it is not the same as the one that are breached. At some point we used the "close" status, but does not anymore.  
![Screenshot 2024-06-24 141418.png](https://community.atlassian.com/t5/image/serverpage/image-id/331415iCC80F68D4A794919/image-size/large?v=v2&px=999 "Screenshot 2024-06-24 141418.png")  

<br />

<br />

Resolved (Below)  
![Screenshot 2024-06-24 141244.png](https://community.atlassian.com/t5/image/serverpage/image-id/331416i1B1E3604DB027983/image-size/large?v=v2&px=999 "Screenshot 2024-06-24 141244.png")


author: Fuji
body: The only pattern I found with the breached tickets, is that in all of them the assignee is assigned after the resolved status and resolution of done are set.  

Below is an example of that.  
![Screenshot 2024-06-24 151745.png](https://community.atlassian.com/t5/image/serverpage/image-id/331432iF17C83EF5CB7267C/image-size/large?v=v2&px=999 "Screenshot 2024-06-24 151745.png")  

Although it does not make sense to me, that this should be the reason?


author: Ash Yadav
body: For starters I'd fix the issues that are closed with unresolved resolution, that's a reporting headache within itself.

Second, have you got any automations running or custom post-functions in the workflow? Anything that re-triggers a workflow transition on assignee for example?

KR,

Ash


author: Fuji
body: How would you fix those issues that are closed with unresolved resolution?   
By opening and resolving them again?  
Also, they are very old and not as important.


author: Fuji
body: These are the only post functions in our workflow I can find.  

![Screenshot 2024-06-27 163052.png](https://community.atlassian.com/t5/image/serverpage/image-id/332148iAC0204082737454C/image-size/large?v=v2&px=999 "Screenshot 2024-06-27 163052.png")

![Screenshot 2024-06-27 163030.png](https://community.atlassian.com/t5/image/serverpage/image-id/332149i89BCDAFC1349D84D/image-size/large?v=v2&px=999 "Screenshot 2024-06-27 163030.png")


author: Vitaly_Berezovsky_SaaSJet
body: Hi [@Fuji](/t5/user/viewprofilepage/user-id/5280741)

Try our [SLA Time and Report](https://marketplace.atlassian.com/apps/1220741?utm_source=Atlassian_Community&utm_medium=refferal&utm_campaign=Comment_Resolved-Done-issues-sudden-breaches-after-long-time_20240621) add-on for Jira with SLA Chart Reports.

How it works:

You can get a helicopter view of necessary issues' SLA statuses using **graph reports** at SLA Time and Reports. Just click the icon at the left top bar.

![1.png](https://community.atlassian.com/t5/image/serverpage/image-id/331093iCFE32DEB986DD8FD/image-dimensions/432x275?v=v2 "1.png")

You can view data by using 3 kinds of chart views:

* Pie Chart (SLA Met/In Progress/Exceeded)

* Line Graphs (SLA Met \& Exceeded)

* SLA Met vs Exceeded per Assignee

SLA Met \& Exceeded issues {#toc-hId--354325780}
------------------------------------------------

### **Line Graph of SLA Met \& Exceeded issues** --- shows dynamic and statistic data of met and exceeded issues for SLA config's goals. {#toc-hId-336235694}

![2.png](https://community.atlassian.com/t5/image/serverpage/image-id/331094iA1EF4CB281726448/image-dimensions/534x249?v=v2 "2.png")

The chart shows detailed information about the number of issues that have met and exceeded SLA goals. Also, you can exclude SLA goals to view chart data without them. If SLA Config has more than one SLA goal, the data will be displayed about each one.

For this type of report you can select the **frequency of splitting data** on the chart: daily, weekly, or monthly.

![3.png](https://community.atlassian.com/t5/image/serverpage/image-id/331095i90E4D94311C8B056/image-size/large?v=v2&px=999 "3.png")

We have a [30-day free](https://marketplace.atlassian.com/apps/1220741?utm_source=Atlassian_Community&utm_medium=refferal&utm_campaign=Comment_Resolved-Done-issues-sudden-breaches-after-long-time_20240621) trial period. Try [SLA Time and Report](https://marketplace.atlassian.com/apps/1220741?utm_source=Atlassian_Community&utm_medium=refferal&utm_campaign=Comment_Resolved-Done-issues-sudden-breaches-after-long-time_20240621) for Jira today!


Tags: jira-service-desk-cloud

jira-service-management

jira-service-management-cloud