-
Type:
Bug
-
Resolution: Not a bug
-
Priority:
Low
-
None
-
Affects Version/s: 4.20.11, 5.1.0
-
Component/s: Reports
-
None
-
1
-
Severity 3 - Minor
Issue Summary
This is reproducible on Data Center: yes
Steps to Reproduce
- Create a new SLA - Time to assignment
- Set the goal for 1 minute
- Start Condition: Create issue / Stop condition: Assignee: From Unassigned
- Create 2 test tickets
- Test-1 wait until Time to assignment breaches
- Test-2 add an assignee before it breaches
- Go to Reports, SLA met vs breached
- Create a new series using "Time to assignment"
- The Report shows only one ticket with SLA met
- If you go back to Test-1 ticket (already breached) and set an assignee the Report starts showing this ticket under breached
Expected Results
The report should show two tickets, one with SLA met and another with SLA breached
Actual Results
The report only shows one ticket, the one with SLA met. That happens because for breached series, the report is using in the background (<SLA Name> = completed()), so it won't consider tickets who's SLA is on going, in this case, Assignee still Unassigned.
Workaround
To by pass this behavior you can use the Created pre-defined series:
![]()
![]()