Using original SLA set for a project after issue moved in jira service desk

Hi Team,

I have set SLAs for Project A and Project B.

 

Goal for Time to Resolution SLA in Project A - 1 hour

Goal for Time to Resolution SLA in Project B - 1 hour

 

The SLAs start executing for Project A and now an issue is moved from Project A to Project B, the goal time remaining for this issue in Project A is 50 minutes.

 

The issue moved to Project B. In Project B, the Goal for this issue starts from 50 minutes as it got moved from Project A.

 

But I want to start Goal for this issue in Project B from 1 hour as SLA defined for this project is 1 hour, even though it is coming from Project A.

 

Kindly help.

3 answers

Hello,

I have exactly the same issue, any answers or workaround?

 

Best regards,

Imane

I have exactly the same issue, any answers or workaround?

0 vote
Jack Brickey Community Champion Jun 27, 2017

Have you tried to create a new SLA in project B for 'moved issues'? I beleive you should be able to setup an SLA for issue created and use a JQL statement to associate the SLA for moved issues. What you likely will need to do is to create a custom field let's call it 'moved issue' that gets filled in when an issue is moved. Then the goals section of the 'moved issues' SLA could fliter on those. In this way you retain the original Time to Resolution SLA for issues created in the project and have a new SLA for moved issues. I'm thinking that you this would also allow you to have two SLA going if you wanted: one with the original SLA time and one w/ a new time. If you did not want that you can edit the Time to Resolution SLA to not include "moved issues".

LMK if this doesn't make sense or doesn't work.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Jun 14, 2018 in Jira Service Desk

How the Telegram Integration for Jira helps Sergey's team take their support efficiency to the bank

...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...

786 views 5 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you