Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Fixed
Priority: Low
Fix Version/s: 3.3.0
Affects Version/s: 2.1.2
Component/s: SLA
Labels:

Symptom Severity:
Severity 3 - Minor
Bug Fix Policy:
View Atlassian Server bug fix policy

Description

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.

Attachments

Issue Links

duplicates

JSDSERVER-747 SLA not appearing on issues moved to Service Desk project

Closed

relates to

JSDSERVER-3562 SLA disappears if "Stop" condition refers to a past event

Closed

JSDSERVER-6835 Jira Service Desk SLAs don't work for items moved between projects

Gathering Interest

mentioned in: Page Loading...; Page Loading...

was cloned as: IL-236 Loading...

(1 was cloned as)

Activity

People

Assignee:: Matthew McMahon (Inactive)

Reporter:: Vikas Sharma

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 23/Jul/2015 6:45 PM

Updated:: 30/Apr/2020 10:56 PM

Resolved:: 31/Jan/2017 5:53 AM

SLA is not updated when an issue is moved