Low Issue Summary
SLA is ongoing when issue moved to to a different project rather than restarting.
This is reproducible on Data Center: yes
Steps to Reproduce
- Create two Service Management project and use same workflow - ProjectA and ProjectB
- Create two identical SLAs in these projects - one each. Set a goal and apply to all remaining issues. Set a starting and closing status
- Create an issue in the first project - ProjectA. Make sure there's a request type associated with this issue type.
- Change the issue status to the one where SLA starts and allow some time for SLA to run
- Move this issue to ProjectB with same issue type
Expected Results
SLA stops and starts fresh in the new project with the goal set in the second project to where issue was moved
Actual Results
SLA is ongoing and not stopped. The SLA continues with remaining time in the SLA goal from previous project
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- duplicates
-
JSDSERVER-5210 Set new SLA for a issue after moved to another project SD
- Gathering Interest
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|