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.
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.
The Jira Service Desk marketing team is working on a guide to help new Atlassian customers switch from email to JSD and we'd love to hear from you! Please share: - What made you realize that i...
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!
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