-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
3.14.0, 3.15.0, 3.16.0, 4.0.0, 4.1.0, 4.2.0, 4.5.5
-
10
-
Severity 3 - Minor
-
5
-
Issue Description
When looking at a Service Desk report about breached SLA, the number of issues for the most recent period (day, week, month) always has the value "0", regardless of how many issues belong to this period.
Steps to Reproduce
- Create a new Service Desk project
- Create a few issues in this project
- Wait for the "Time to Resolution" SLA to breach for these issues, or simply edit the goal for this SLA to 1 minute, so that these issues can breach quickly
- Go to the project report page
- Create a new report with the series "Time to Resolution (Breached)"
- Look at the number of issues listed for each date, and noticed that for the most recent day, it is showing "0":
- Click on the "0" link next to the most recent day, and notice that all the breached issues are returned there, even though there was "0" result shown on the previous page:
Observed
The number of issues that belong to the most recent period is shown as "0".
Expected
This number should match the actual number of issues that we see when clicking on the "0" link
- relates to
-
-
- Closed
-
- is cloned by
-
JSMDC-6966 You do not have permission to view this issue
- is related to
-
SSE-623 You do not have permission to view this issue
- links to
I dont understand the ticket status here, why it says Gathering Impact? If its bug has to fix in new release.
Its not something enhancement people are looking for.
We see this issue on JSM 5.12.10, where breached count is showing 0.