I have a project and a Service Desk portal for an organization we are working with, with 4 customers from that same organization. How can I give them the ability to see other customers tickets so they don't duplicate tickets and report the same issues twice?
It would be very helpful if any member of our customer organization could see all the tickets for their organization–it would give them a nice overview of our ongoing work with that organization.
It occurred to us that we could have customers add each other as Requested Participants (or maybe we could add them with a post function or automation rule) but then I think they'd all get notification emails for all the issues. If we instead have all the customers at the organization share one profile, then only one of them can ever receive notification emails.
It would be great if they could get notifications for the Requests they raised personally, but at the same time be able to view the other Requests that their coworkers have raised.
Also, participants are not enabled by default, so you need to enable it first.
Jaime Kirch da Silveira
Atlassian Cloud Support
In general you seem to be trying to stop people from reporting the same issue twice. That is exactly what the Service Desk knowledge base feature is for.
I think you should have a read through: Providing self-help resources for your customers with a knowledge base
I hope that helps!
The Jira Service Desk marketing team is working on a guide to help new Atlassian customers switch from email to JSD and we'd love to hear from you! Please share: - What made you realize that i...
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