-
Bug
-
Resolution: Unresolved
-
Medium
-
31
-
Severity 3 - Minor
-
30
-
Summary
SLA is not started when starting and pausing the SLA at the same time
Steps to Reproduce:
- Set start SLA condition; "Comment: For Customer";
- Set pause SLA condition; "Status: Waiting for Customer";
- Create a SD ticket and comment as anyone but a participant (meaning not as a reporter or a requested participant). The status will transition after a comment is made.
Expected Results
The SLA for the ticket should be started followed by a pause event. 2 Events saved in the DB.
Actual Results
The SLA field remains empty.
Notes
The START event is not saved in the DB. The pause takes precedence and only the PAUSE event is stored.
- is related to
-
JSDSERVER-1062 If All SLA is not Appearing after Issue is Created, "SLA Modified" info will appear.
-
- Closed
-
- was cloned as
-
DESK-3973 Failed to load
I am unable to get any SLA to trigger when using the Comment: for Customer condition as a Start for an SLA. It would be incredibly valuable to be able to trigger SLAs to begin off of the addition of a comment alone.