The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Customer issues requiring external vendor advice

Leon
Contributor
July 28, 2021

What is the best way to keep track of communication with a vendor on a customer issue.

Eg A customer raises an issue however it requires us to obtain advice from a vendor.

We do not want to add the vendor as the participant as it will allow the customer and vendor to communicate through jira comments.

We want to engage in a conversation with the vendor about the customers issue, linking or keeping all conversations together without letting the customer know the advice is coming from the vendor.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 29, 2021

I would consider using organizations within your JSM project. Set up your vendor as one organization and your customer as another. You won’t be able to share across organizations, given your requirement to keep the customer out of the loop, but you can create a linked issue (relates to) for the vendor communications. That way you have two tickets one where your agent communicates with your customer back-and-forth and one where your agent communicates with a vendor back-and-forth.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events