My staff and my customers can use the feature "Add participants" to an issue. But I have problems with email notification.
The new participant is notified only if the Add on notifications are enabled. But if Add on notifications are enabled, my customers receives on each comment two notification (one for a new response, a seconde for a status changed, see this issue).
If I disable the Add on notifications and use only the project notification, I can't find a way to notify my customer when he is added to an issue or when a comment is sent.
Have you an idea that could solve this problem?
It's a clunky workaround, but at my office we've created a custom workflow whereby all of the ticket statuses are the same on the customer facing side (just "In Progress") and only change on the internal side ("Waiting for Customer," "Waiting for Development," etc.). Therefore the customer only gets a status update email when the ticket is first opened and when it's finally resolved, but they still get emails (just one) when a comment is added.
That might be an option for you?
The important piece of the puzzle is accessed from Service Desk > Settings > Request Types > Edit Fields (you'll have to do this for every single request type you have set up) > Workflow Statuses (tab at the top next to "Fields") Here, you can set multiple workflow steps to the same customer-facing status. For example, in my workflow I have the following mappings: Open > Open (tells the customer we received the ticket but no one has looked at it yet) In Progress > In Progress (tells the customer the ticket has been triaged and we're actively looking into the issue) Waiting for Customer > In Progress (customer still sees that we're working on the issue) In Development > In Progress (still working on the issue...) Resolved > Resolved (customer sees issue has been resolved but internally we're not done documenting or whatever) Closed > Resolved (customer still thinks the issue is resolved but internally we're entirely finished with the issue) Therefore, the customer-facing status never changes when the ticket transitions from in progress to waiting for customer and they'll only get a status change e-mail when the ticket is first moved to "In Progress" or when it's finally set to "Resolved." Hope that helps!
Hi @Simon G.
In JIRA enabling the outgoing mail log in
Admin -> System -> Troubleshooting -> Logging &profiling.
turn it on along with debugging, then check the log to see if Jira has sent duplicate mails to same user.
for more details refer this KB article.
It's not a problem of duplicate mail:
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...be more productive while being fun to use at the same time. For some, getting started can be a bit intimidating. This is especially true if Jira Service Desk is your first exposure to Atlassian...
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