The scenario for this is a request comes in to the service desk and we want to then break it out as an issue(s) for one of the 2nd tier support groups which exist in a seperate JIRA core / software project. Ie a DBA task. We cant track these as subtasks as there will be subtasks off the new issue , ie the request for a database change comes in through our service desk portal. This needs to be moved to our DBA team as multiple subtasks off a newly created and linked issue to the parent issue in JSD. The SLA needs to be applied to all the other related issues.
How can we do this?
Firstly, you should know that SLAs work within the JSD project and only.
So if the escalated new issues are in projects that are not ServiceDesk projects you cannot put SLAs.
Finally, in order to avoid using post functions to create issues, I would suggest the addon of Bob Swift Clone+ It gives you the right to clone the issue to another project and autolink them.
Now, if you must put SLA on the time that you are waiting a response on the linked issue, you can create a simple step/transition on your workflow "Escalated" and put an SLA on that Status.
I hope that helped.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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