-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Medium
-
Component/s: SLA
-
3
-
Severity 3 - Minor
Problem
SLA starts running or is breached(depening on the elapsed time) if the SLA pause status is first in the workflow
Steps to Reproduce
- Create a SLA with below conditions

- Workflow has "Waiting for support" as the starting status

- Here, if we perform a self loop on "Waiting for support", the SLA starts running when it must still be in a Pause state.
The problem does not occur for any other status in the workflow, it happens only when its the first status.
Expected Results
SLA must be in Paused state.
Actual Results
SLA starts running.
Workaround
- Don't have the self transition on this status
- or don't set the first status as the Pause condition
- or add one more status before this in the workflow
- mentioned in
-
Page Loading...