Issue Summary
SLA does not stop if the "Resolution" has been twice in the same workflow transition.
For example, setting a "Resolution" field through workflow transition post function, whilst closing the issue through REST endpoint and setting the "Resolution" value within.
This is reproducible on Data Center: yes
Steps to Reproduce
- Modify used workflow and add a post function to set Resolution field (e.g. to "Done"). Publish the workflow
- Create a SLA that has Stop condition "Entered Status: Done"
- Create a JSM issue that has the SLA from step 2 applied, and running once the issue is created
- Close a request through REST endpoint for issue transition. Make sure to include "Resolution" value "Done" in the REST request body.
Expected Results
The SLA stops, regardless if the issue has been closed through REST request or through UI.
Actual Results
The SLA keeps running once the issue has been closed through REST endpoint.
Workaround
Workaround 1
One needs to make sure that the "Resolution" value is set only once:
- Through Workflow screen pop-up,
- Through Workflow post-function,
- or through REST request.
Workaround 2
Move the post function step to after the issue history event, then the problem can be avoided as JSM will see the original history item.
- causes
-
JSDSERVER-16282 Editing an issue as an agent starts an SLA configured for Resolution: Cleared event
-
- Closed
-
- is related to
-
JSDSERVER-16082 Add a healthcheck or similar to warn Administrators if the post function configuration is not compatible with SLA configuration
- Gathering Interest
- is resolved by
-
JRASERVER-78674 Resolution change is missing from Issue history if Resolution is set via the UI and a workflow at the same time
-
- Closed
-
- links to
- mentioned in
-
Page Loading...