-
Bug
-
Resolution: Answered
-
Low
-
None
-
2.5.8
Summary
SLA didn't stop when the agent make a Comment:For Customer at issue under their own name . Meaning the agent is the Reporter of the issue .
Steps to Reproduce
- Configured Time to Resolution have Comment:For Customers and Entered Status:Waiting For Customer at Stop
- As a agent , create a issue .
Unable to render embedded object: File (Screen Shot 2015-10-01 at 10.33.38 PM) not found. - Comment the issue . The SLA didn't stop. Which is incorrect behaviour.
- Click Transition Response to Customer . The SLA stop.
Expected Results
When agent entered a comment to the issue , eventhough he is the reporter of the issue , the SLA should stops.
Actual Results
SLA didn't stop when entered a comment to the issue that raised by himself.
- has a derivative of
-
JSDSERVER-1462 Raise request on behalf of customer through email
- Closed
-
JSDSERVER-3506 Provide automation conditions to allow removal of Request Participants
- Gathering Interest
-
JSMDC-353 Loading...
- is duplicated by
-
JSDSERVER-3504 SLA does not pause when commenting on the issue as participant
- Gathering Impact
- relates to
-
JSDSERVER-3390 Automation does not trigger when agent is listed in Request Participant
- Closed
-
JSDSERVER-5680 The condition "Comment:For Customers" in an SLA configuration is not verified when an agent is part of the same organization as the customer
- Closed
-
SSE-546 Loading...
- mentioned in
-
Page Loading...
- was cloned as
-
DESK-4406 Loading...