I'm using a Next-Gen Jira Service Desk project, and when a user reports an issue via email, and they also cc a mailing list of which they are a member, they receive duplicate notifications on updates.
I found this article about troubleshooting notifications and this exact problem is listed there, but with no offered solutions:
Check the notification scheme to see if it contains a mailing list - if it uses a mailing list and another notification item such as Assignee, and the assignee is also within the mailing list, JIRA applications are not able to identify the users of the mailing list and will end up sending duplicate notifications.
It is a pretty common situation for a person to cc their team to give them access to the ticket and notifications, so we'd really like to solve this.
Here's a list of things we've tried that did not work:
I understand that the root of the problem is that the mailing list membership is unknown to Jira: it doesn't know that the reporter is also a member and thus it just blindly sends notifications to the reporter and all the mailing lists in Request Participant.
Is there any plan to add deeper integration of gsuite into Jira? I saw that Atlassian Access has gsuite sync, but syncing groups to Jira is not enough - the Jira mail handler needs to know which mailing lists correspond to groups and then do the right thing.
Are there any other solutions to this problem?
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
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