We are evaluating JIRA Service Desk and plan to use it as Self-Hosting (Server). We are going through the documentation and have some questions.
Can an external third party be involved via email?
Example: A customer mails a request and it is turned into an issue. To solve the issue the agent has to contact an external third party via email (WAITING FOR THIRD PARTY). The external third party answers via email and the issue status is updated. The agent can process the issue and solve/close it.
Is that possible?
Any help would be really appreciated. Thank you. :-)
Hey Susi - I guess this was just implemented in the latest version of JIRA Service Desk. Otherwise you could add the third party to the issue so that they can answer via email (which leads to the creation of a comment that the customer can see too) or you create a separate issue for the communication with the third party in the JIRA Service Desk project so that the customer does not see the comments.
Any special reason you don't want to have the third party being involved as a Service Desk collaborator (consuming a normal JIRA license, no Service Desk agent)?
I have the same question. This is how it works for us:
We handle issues/requests for our customers, but we are partner with multiple third parties. Most of the time we would have to ask the third party what to do with the request. We want to forward the issue, 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.
What do you mean with adding the third party to the issue? How do I do this?
by adding the third party to the issue, I meant adding them as a participant to the issue. This leads to their comments being visible to the customer. If this is no option, you could create JIRA users for each third party and add them to your Service Desk project as collaborators (so that they can comment but their comments won't be visible to the customer). This way they can see all the issues in the Service Desk project so you might want to use a security level per partner and an internal security level as default.
Hope that helps
you're welcome. With collaborators I mean JIRA users which are added to the Service Desk project as non-agents but are using JIRA (so also consuming JIRA Software/Core licenses). Another option could be the JETI add-on (https://marketplace.atlassian.com/plugins/com.metainf.jira.plugin.emailissue/server/overview) to forward issues and receive replies but I would recommend to test it in a testing environment first and see if you can configure it so that it works your way.
I have a similar request, we have a number of third party vendors that have their own ticket system. We would like to track the communications between ourselves and the third party in the same Jira ticket, however keep them as internal communications.
Ticket is raised by client, we need to involve third party vendor, ideally from a custom drop down field, we select the vendor and the comments get sent to that vendor. They reply via email and the comments get update but only visible by us internally.
The vendor response could be too technical for the end user or contain information held under an NDA.
We would then decide on the next step to the client.
Do you have any examples on this type of workflow.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...+ 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...
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