-
Suggestion
-
Resolution: Unresolved
-
3
-
37
-
Problem Definition
Currently there's no built-in feature to disable @mention notifications for a specific project.
Suggested Solution
As an admin, I should be able to disable/enable the @mention email notifications for any project.
Why this is important
This functionality could help to prevent sensitive information to be exposed when the @mention feature is being used.
Workaround
There are two things that allow @mention to work.
- The @mention uses the Browse Users global permission to determine whether they will be able to see the user list or not. So to prevent this you can remove all groups in the Browse Users global permission so your user would not be able to search for the user at all. The downside of doing this is you would not be able to search for the user even in any other field such as Assignee or Reporter. For more details please see Managing global permissions.
- The comment field needs to be of Wiki Style Renderer. By default; fields like Description or Comment is set to Wiki Style Renderer. If you change it to Default Text Renderer in your Field Configuration; you will no longer be able to use @mention. However, you'd also not be able to styling your text in the Comment any more and you can't no longer use tags such as the code tag. For instructions please refer to Specifying field behavior.
- was cloned as
-
- Gathering Interest
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-69612] Ability to disable the @mention notifications for a specific project
Temporarily changing the Roles/Permissions as advised in workarounds section seems like a working and straight way solution, and promptly turning it back right after a migration (forgetting is not an option as non-professional).
Even it's a production, having a pre-defined maintenance and down-time is a common practice.
Considering other more critical feature requests, would be great to have Atlassian cover those first.
This functionality should not be considered a feature, but rather a significant inconvenience/annoyance.
Approximately 850 users have been annoyed by email notifications during a migration/refactoring process. It is unsettling when management reminds you about old closed tickets for which they receive a notification. Currently, I have 3 more JSM projects in the pipeline, each containing hundreds of thousands of tickets . . . how many more am I going to annoy???
The most viable solution appears to disable the instance's SMTP during the migration phase. However, this fix is impractical as it would result in the instance being unable to send or receive emails for an extended period - potentially even longer if I forget to re-enable it promptly.
I kindly request Atlassian to address this inconvenience promptly since it will also impact your new refactoring facility designed for project migrations that you are currently heavily promoting.
What I understand that it should be like and I would not call it a feature, it would be only having the possibility of mentioning users who do have access to the issue (including Issue Security, project...).
This is rather frustrating, we have a slack integration that handles most of this, we should be able to disable mention emails? Why is is not part of the notification policy!
I definitely would like the ability to disable email notifications when someone @mentions another user. We recently implemented the Slack/Jira connector so that our Jira notifications would be seen in Slack instead of email. That's a much better workflow for our team, and cuts down a lot on unnecessary email.
However, when I followed the instructions to disable email notifications, I found that it disabled all email notifications except @mention's. That seems very unintuitive. Why would @mention's be treated differently?
Jira has a lot of ways to customize the product, this ability would be a helpful addition.
Thank you.
It is not unreasonable to assume that the global settings should be possible to be overridden by specific project-related settings. By failing to do so, this opens up the potential for some fairly significant security issues. When will Atlassian be looking in to this? As it's been open since 2018, there really ought to be some kind of update by now.