I am having a huge issue with Jira Service Desk, I'm at the final stage of implementation with live customers.
This is becoming a very pressing issue and we will have to get out of JSD to another platform if we cannot have this basic feature.
Any reason why it was made this way to begin with?
How are other companies using this?
When someone is added on CC they are automatically added as a participant and they receive an email informing this.
It will only work if you let the configuration for customers to create their own accounts. In this case, your Service Desk will not be open, but anyone that sends an email to open a ticket or go to the Customer Portal login page will be able to create their own account.
Also, watchers are only internal users with a license, it will not be possible to add external people as watchers.
You can find more information on the link below:
Welcome to Atlassian Community!
To ensure that anyone added on the CC will be added as a participant, you need to allow customers to create their own accounts.
First, you need to go to Project settings > Customer permission > Who can customers share requests with? > Any customer or organization, by searching this project > Save.
Them, go to Jira settings > Products > Configuration > Can customers create their own accounts? > Yes, by signing up or sending a request.
Please, give it a try and let us know how it goes.
@Angélica Luz can you help me with this:
(1) JSD Cloud
(2) Several customers within several organizations
(3) Customers who send email to support@ also cc: other users within their organization and also JSD agents in the to: or cc: fields
(4) Who can customers share requests with? Other customers in their organization.
Problem is when a customer writes to support and cc: or to: to other customers from his organization and some agents, it only creates JSD issue with the reporter (sender) only.
Can it be solved with some Custom mail handler options or something?
Thank you for reaching out to Community!
Participants are only added if they are added in CC field. If people are added on TO, they won't be added.
Also, the project must be open for customers to create their own accounts.
First, you need to change the customer permission to Who can customers share requests with? > Any customer or organization, by searching this project.
After that, you need to go to Project settings > Products > Configuration > Can customers create their own accounts? > Yes, by signing up or sending a request.
It means that if the customer adds someone to CC that does not have an account, Jira will create an account and they will be added as participant.
@Angélica Luz thanks I got it.
My issue here is that I don't want customers able to create accounts on their own and also don't want customers able to share with other customers outside his organization (we have several organizations as clients with several customers within we give support to).
We create by API all the org and customers that come from our internal app, so that assures us no one is left without a portal account.
I tried for a test Customer 1 emails these ways and the result is the following:
To: Customer 2
cc: JSD Agent
cc: Jira User
Assignee: JSD Agent
Reporter: Customer 1
Request Customer 2
Watcher: Jira User
Even if the Jira User, Customer 2 and JSD Agent are permuted between To: and CC: fields the result area the same.
Thank you for the details Sebastián.
I believe that this issue is related to a bug. If a customer adds someone that is not part of the organization, nobody will be added as a participant.
As they are adding an agent as CC, they are part of the project, but not part of the organization.
Note that, it's not recommended to add an agent in an organization or as a participant, because they will not receive notification since they will be agent and customer at the same time and Jira won't know what type of notification to send.
Agents must be only assignee or watcher.
Thanks, @Angélica Luz I was exactly asking that kind of pros and cons in this one:
When you say "If a customer adds someone that is not part of the organization, nobody will be added as a participant" you are referring someone = as any customer in his org?
Cause when someone is an Agent or Jira User works fine with the test we have been doing.
Thanks for your insights on this!
No, I was referring to users that are not part of the organization. An agent can’t be part of an organization on a service desk project and they can’t be added as a participant, otherwise, notifications won’t work for them. An agent must be only watcher or assignee.
@Angélica Luz Please ask your team to update the wording for the setting, "Who can customers share requests with?".
The third option should read something like, "Any customer or organization, by searching this project. This option allows them to search all customers in the current project and allows email requests to automatically add request participants through CC."
We dealt with this problem for several weeks before finding this thread and fixing the problem. A simple wording change could have saved us hundreds of hours in lost productivity.
You have to check two settings
1- "Who can customers share requests with?". it should be allowed
2- on JSD project go to customer notifications or if you created any automation rule for notifications , in that rule you must select who can receive notifications (reporter and customers involved)
Customer involved contains participants, if any of your notification does not have this option, they will not receive any ticket updates
Hi Atlassian Community! This is Teresa from the Atlassian team. My colleague Paul Buffington @Buff and I are excited to share a brand new ITSM resource we’ve created – "The Complete Guide to At...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events