-
Bug
-
Resolution: Fixed
-
Low
-
2.1.2
-
Severity 3 - Minor
-
We have a project "A" where SLA is set for "Time to Resolve". SLA is not defined in project "B"
A ticket was created in project "A". The ticket was moved from project "A" to project "B" and it was resolved in project "B". Later the ticket was moved back to project "A". SLA clock never stopped in this case and it is still running. It affected team's metrics.
SLA value should update based on the current project and ticket status.
- duplicates
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
JSDSERVER-6835 Jira Service Desk SLAs don't work for items moved between projects
- Gathering Interest
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
- was cloned as
-
IL-236 Loading...
[JSDSERVER-2134] SLA is not updated when an issue is moved
| Link | New: This issue relates to JSDSERVER-6835 [ JSDSERVER-6835 ] |
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2303956 ] | New: JAC Bug Workflow v3 [ 3126211 ] |
| Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
| Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
| Remote Link | Original: This issue links to "Page (Extranet)" [ 347077 ] |
| Remote Link | New: This issue links to "Page (Extranet)" [ 351206 ] |
| Remote Link | New: This issue links to "Page (Extranet)" [ 347077 ] |
| Remote Link | New: This issue links to "Page (Extranet)" [ 347142 ] |
| Labels | Original: affects-server cqt investigate need-investigation | New: affects-server cqt cst investigate need-investigation |
| Workflow | Original: JSD Bug Workflow v5 [ 2057924 ] | New: JSD Bug Workflow v5 - TEMP [ 2303956 ] |
Suggestion logged: JSDSERVER-6835