I believe this is happening because of your project's notification scheme. You'll have to go to your respective JIRA Project and alter the Notification scheme not notify users when issues are updated. Check this documentation as it explains in detail how notification schemes work: https://confluence.atlassian.com/display/AOD/Creating+a+Notification+Scheme
Hope it helps!
With the new release of JIRA Agile the "sprint" field officially became a "first class citizen" as Atlassian says, right? The only way to control emails in the project notification scheme is if an issue is updated... but is there a way to get down to the field level and say "do not send an email update when an issue is added to the next sprint" ?
Nick and Brian,
I've managed to work around the issue by using bulk change. I use bulk change to set the sprint field to the value of the new sprint and suppress the emails via the bulk change suppression mechanism.
It's definitely a sub-optimal solution for two reasons. Firstly, during bulk change, the Sprint field doesn't seem to recognize the string name of the Sprint and, instead, must have the integer Sprint ID. It's difficult to get the numerical Sprint ID. Perform a Google search on "JIRA Agile Sprint ID" to get some suggestions. The second sub-optimal characteristic of my work around is that suppression of bulk-change emails requires project admin privileges on all projects which contain issue to be modified. I happen to have those privileges, so I can suppress the emails. Perhaps it's not a stretch to imagine that your sprint planners will also have project admin permissions but it's not ideal for sure.
Nice work around. But I agree it is far from optimal and it wouldn't work for my group. I was shocked that sprint is not an email notification setting. For my group I am typically not the one adding issues to a sprint. We are using it in a Marketing setiing and have several product owners that each add their own issues to a single sprint. And these individuals are deciding what to add from the sprint planning mode in JIRA Agile. So knowing which issues to bulk change would be very diffiucult.
At Atlassian, we believe in our own products – that's why we use them, even at the enterprise level. Doing so gives us first-hand experience of how they perform at scale; to do this, we monitor each ...
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