Forward ticket to external helpdesk

I was trialling Service Desk and had following requirement:

 

* Internal user sends email to helpdesk 

* Ticket is created

* Agent looks at it and sees, ok its a ticket for our third party supplier. 

* Agent forwards the ticket to the external supplier email address

* External supplier email system comes back with a ticket number

* Agent replies and goes back and forth with external supplier

* When issue is solved with external supplier comment is given to internal customer 

* If all good agent closes internal ticket.

 

I cannot really find a way how to deal with this using Jira service desk as there seems to be no forward ticket to email option?

1 answer

0 votes
Jack Brickey Community Champion Nov 15, 2017

@Koen van Besien, the key is in your 4th bullet. What do you really want to do relative to forwarding the ticket. There are various approaches to incorporating third-parties into your ticket resolution process. You can give the third-parties user accounts w/in JIRA with certain permissions that meet your needs or you can keep them completely out of the application in which case you would need another method to communicate, e.g. email. I'm not a fan of email as it makes things very manual. I would be more in favor of incorporating the third-party into JSD or JSW.

If we consider the options for incorporating them into JSD/JSW then consider how much you want to expose them to or give them access too. Here are some options:

  • make them Agents of the project. This gives them full access to all issues in that project. Likely not what you want but it is nice a clean implementation. In this way you can use Components to capture the third-party and have the issues default to the third-party agent when the component is set, but there are other options here too.
  • Create a separate project for the third-party, making them agents there and then from the original internal project create a linked issue in the third parties project. In this scenario the third-party has visibility and control on only their issues. You can even use Automation function to transition the original if desired which can help alert the internal project agent to take an action, e.g. close the original and add comment.
  • similar to the second bullet but make the third party a Customer instead of an agent. the only advantage here is to control cost. In this scenario the third-party can't be assigned the issue and is limited to comments only so your agent will need to own the issue to closure.

hopefully these thought help you consider the best approach. BTW, you can add a custom field in in case and include the third-parties customer ticket number for reference.

Thanks for your thoughtful reply.  The main issue is that the external party have their own helpdesk.

So what basically happens is that the agent needs to create a ticket in an external third party help desk system. We currently do that by just sending an email to their support desk which creates a ticket automatically and returns an email with the ticket number. ITs this email you use to go back and forth and when you came to a conclusion, the agent can update the internal ticket with a summary of the discussion with the external party. Hope that explains a bit what I am after. 

Its mainly that you would like to have all the communication inside of the Jira service desk so that it does not sit in one of the agents personal email accounts. 

You could of course link up the ticket number of the other helpdesk and use that to click on and do the communication (as you already mentioned) but in a perfect world you would like to have that communication in the Jira Service desk. Maybe as a "Sub ticket" or just a linked ticket but then the starting email should come from the Jira service desk I think?

Hope that explains a bit what I was after!

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

674 views 4 15
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot