I have two project with 2 metrics SLAs.
Goal for Time to Resolution SLA for Project 1 in Project 1 = 4 hour
Goal for Time to Resolution SLA for Project 2 in Project 2 = 1,5 hour
The SLAs start executing for Project 1 and now an issue is moved from Project 1 to Project 2, the goal time remaining for this issue in Project 1 is 60 minutes.
Present:
The issue moved to Project 2. In Project 2, the Goal for this issue starts from 60 minutes as it got moved from Project 1. Remaining time for this issue in Project 2 is 30 minutes only.
Expected:
The issue moved to Project 2. In Project 2, the Goal for Time to Resolution SLA for Project 1 is stoped on 60 minutes, and Goal for Time to Resolution SLA for Project 2 start from 0 minutes.
Sugestion:
Add to SLA metric (Start, Stop, Pause on) option Move conditions
- is duplicated by
-
JSDSERVER-14783 SLA is ongoing rather than restarting when issue moved to to a different project.
-
- Gathering Impact
-
- relates to
-
JSDCLOUD-8408 Reset SLA when issue is moved to another Service Desk project
- Gathering Interest
- links to
