Convert internal Service Desk comment to shared with customer


As an Agent I want to make an internal comment made by a Developer visible to a Customer.

The idea is to edit the Developer's comment as an Agent (the blue button "Share with customer" is visible and active), but when pressed the edited comment is not published to a Customer portal.

Are there some permissions to set for a Developer Project role?

Thanks for the answer or suggestion how to make a workflow.


2 answers

The idea of JSD is that only the Agent can interact with the customers. You cant set permissions to allow a developer to comment to an customer.

Yes, that is why I (as an Agent) want to have an option to somehow edit/clone/approve the Developer's comment to be shared with Customer.

Currently the Developers are communicationg with Customers directly by email and phone. This makes resolving issues quick, but messy and we want out of that email communication hell.

So, I am looking for a middle ground, a solution which will not create a bottleneck on an Agent and will still make communication efficient.

Any idea?

0 votes
Jack Brickey Community Champion Aug 22, 2017

@Semi Kefi [demicon GmbH],

This is exactly why there are internal and public methods. The developer (collaborator) places a 'wordy' comment into the ticket the Agent, wanting to share some but not all of the details, will copy the comment into a new comment and edit for customer consumption then click Share with customer.

Thanks Jack, I am well aware of the current intended workflow, but...there is always a "but".

We, and I am sure many others, have a case where Customers are tech-savvy and can handle well written answers from Developers (Collaborators).

It is a waste of time for an Agent to manually copy/paste/reword the Developer's answer if he/she determines that the Developer's answer is valid. So, I think there should be an option for an Agent just to elevate/approve and share the answer forward to a Customer. That is quick and responsibility is still in Agent's actions. As a side effect, the Developer and the Client will not be inclined to communicate via any other channel if they would not be satisfied with the delay Agent can cause.

I think this is a very valid scenario Atlassian should consider.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 15, 2019 in Jira Service Desk

Are you a Jira Service Desk agent? We want to talk to you!

Are you a whiz at handling tickets and looking at how you can further optimize your workflow with automation? Do you tackle detailed customer support questions while simultaneously getting flooded wi...

177 views 0 8
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