Details
-
Suggestion
-
Resolution: Unresolved
-
25
-
61
-
Description
NOTE: This bug report is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding bug report.
Steps to reproduce:
- Apply JIRA Service desk to an existing project that has 30 days+ old issues.
- Navigate to the SLA reports in JIRA Service Desk and select SLA met vs breached report.
Expected Behavior:
The report should present the breached issues for the past 7 days, 14 days, 30 days, etc accordingly.
Actual Behavior:
The report is actually counting older issues as breached with the date the service desk was applied to the project and not with the correct date when it was really breached.
As you can see on the screenshot below, the project in question had breached issues on October 2014. After applied the the Service Desk to this project it's now counting as breached with the date the Service Desk was applied to the project (Feb 13th).
Workaround:
No available workarounds.
- (Community Post) SLA Reports Showing Incorrectly Breached Tickets
- Hope this helps!
Attachments
Issue Links
- is related to
-
JSDSERVER-1512 SLA Report not working as expected (SLA met vs breached)
- Closed
- relates to
-
JSDCLOUD-5538 SLA reports showing 0 in Summary table
- Closed