Does anyone knows what mechanism JIRA Service Desk uses to prevent the regular JIRA notification from firing?
We have a setup that catches issues that are created from email, and adds the proper "Customer Request Type" field, which makes them into valid Service Desk issues, so they show up in the customer portal and get the service desk formatted emails.
However, these issues also send the regular JIRA event emails, while issues that are created from the portal do not. So what's the magic?
Been doing a lot of testing with the new release and we aren't having this problem, only one message goes out to the reporter.
Depending on who responded and the service team user settings, regular Jira notifications go out to the service team members.
So if the reporter also happens to be a regular JIRA project user, then they would be receiving 2 emails, one from the default JIRA notification settings and the other from the JIRA Service Desk settings? Is there anyway to change the notification settings to silence the regular JIRA one in these cases?
...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