We have the autowatch feature enabled in JIRA Cloud. When people create tickets through JIRA then they are added as watchers through the issue. If this same person creates the ticket into the same project through JIRA Service Desk's Customer portal then the reporter is not automatically added as watcher.
Any ideas how to fix that?
Oh and we are using JIRA and JIRA Service Desk in house, so everyone who has access to Service Desk can also access JIRA.
Ok, I figured that maybe it is this way because usually Customers are outside of the company and they should not be getting the issue field updates that are meaningful only to the agents.
But, still. As I tested it out. If I added the reporter as a watcher manually then they did not get the issue field updates anyway. Probably the Service Desk Notification scheme is driving this behaviour.
For now I just created the workaround - added a post function to our workflow, where the Reporter field value is copied to Watchers right after the ticket is created. Not the nicest way of solving the issue but still ..
Why was this an issue?
Because on the System Dashboard we want all the tickets to show in in the Watcher Macro. All issues that you have somehow involvement - wether a reporter or watcher. And as JIRA already has the global configuration to add you as a watcher if you report a issue it mades since to continue to use the same logic also on the issue that are created through Service Desk.
Hello Helly, we just stumbled upon the same problem. In contrast to what you proposed, I get no notifications when I add the reporter as a watcher. JIRA Service Desk will nevertheless suppress notifications for a JIRA User, who is not only a SD customer but also a jira-user. Have you got any other news on this issue? Cheers, Kirstin
Hey Kristin! I decided to turn off the Service Desk notification all together. It made sense to just stay with the 'normal' JIRA notifications as we use the tool inside and two different types of notifications did not make sense to me. In your case.. yeah this is the thing. If SD notifications are enabled than it seems SD notifications are primary .. and some of the normal JIRA notifications on those tickets that were raised from SD are not fired. I was testing it out in different ways (although did not record all of my tests) and this is why I also made the decision to just switch off the SD notifications .. Hope this helps. Cheerio, Heily
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
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