You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am looking for suggestions on how to better handle escalations from service desk (help desk) to another jira project (application development).
How we currently handle
Help desk takes the call and requests escalation from development team. Dev team escalates issue. Issue is automatically cloned and reporter copied issue in the dev project. Help desk closes their ticket as escalated and advises user to follow the newly created ticket.
One problem we encounter is that the reporter no longer has visibility into their open requests from the service desk portal.
It was suggested that help desk keep their issues open until the escalated issue is resolved and follow up with the reporter upon resolution. This leaves us with an overwhelming number of tickets in service desk
Are there add-ons that can handle the follow up once the escalated issue is marked as resolved? Any suggestions on how to better handle the escalation process?
Hi @Chris
There are solutions already for this using paid apps. Mentioning 2 here.
Regards,
Ravi
We use automation to create a linked ticket from our service desk to our dev team. This allows the service desk to continue tracking the request item / incident from our clients and follow up w/ our product owners on SLA as breach becomes near. We also use priority to set expected follow up responses back to the service desk so that they can communicate w/ the customer the progress the dev team is making.