Details
-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Severity 3 - Minor
-
Description
NOTE: This bug report is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding bug report.
I have an issue where JIRA Service Desk Time to Resolution based reports fail to catch issues that had breached before despite using the everBreached() method.
Steps to replicate:
- Create an SLA for issue Status Open -> 1m
- Create an SLA for Issue Status In Progress - 5m
- Remove all other SLS but this and the one meant for All Remaining Issues
- Create a new Report
- Add Series, Time to Resolution-Breached.
- Add a JQL filter ""Time to resolution" = everBreached()"
- Create a new issue.
- Wait for the issue to breach SLA in open Status.
- Move issue to "in progress".
- Close the issue.
- View the "Breached result created above"
Expected Result:
- JIRA would notice the tickets once breached and list them out.
Actual Result.
- JIRA doesn't know that the issue ever breached.
Feature Request:
- Let the result for everBreached() show what state the issue was in when it breached.
Attachments
Issue Links
- is related to
-
JSDSERVER-1796 "Time to resolution" = everBreached() not working in Report
- Gathering Impact
- relates to
-
JSDCLOUD-5538 SLA reports showing 0 in Summary table
- Closed