You’re in a meeting and your coworker says, “Did you see that Jira ticket I mentioned you on?” Most of us might say, “Maybe, I get so many I probably missed it.” or “Who knows, I send all of those to a folder [that I never check].” It may sometimes feel like the more diligently you are using Jira, the more emails you get. You may even get them for your own changes! It’s not that you don’t care, you’re likely just overwhelmed by the sheer volume of Jira notifications hitting your inbox. Notification fatigue can cause major delays when we don’t respond to critical items. Teams may stop using ticket comments altogether because they don’t trust that their coworkers are even reading the notifications.
Luckily, there are a few easy steps we can take to reduce the number of Jira emails received, restricting them to only the tickets you want to watch or comments where you are @ mentioned.
There are two notification options that you may want to turn off: Watch your issues and Notifications of your changes. Follow the steps below to find and modify them.
For more information about these preferences, see the Jira Cloud Documentation on this topic.
There are two notification options that you may want to turn off: Autowatch and My Changes. Follow the steps below to find and modify them.
For more information about these preferences, see the Jira Server Documentation on this topic.
When you set Watch your issues/Autowatch to disabled, as described in the previous section, it will only apply for future tickets you interact with in Jira. For all those previous tickets you are already watching, you should remove yourself as a watcher and see your inbox quickly become manageable again.
Copy and paste this text into the search textbox:
issue in watchedIssues()
When viewing your search results, select the … option menu on the top right of the screen. In the option dropdown, select Bulk change all ### issues (where, ### represents your number of total results). You will be sent to the Bulk Operation screen*. There are 4 steps to finishing the bulk changes:
*Note: If you can’t find this menu option, you may not have the Make Bulk Changes global permission. Check with your Jira Administrator.
If the Bulk Operation was successful, you will not have any search results when you return to the Search screen.
By default, if you are listed as the Reporter or Assignee you will always get notified of changes others make to that ticket. This is controlled by the Issue Updated Notification in the Notification Scheme assigned to the project.
Check with your Jira Administrator to see if it makes sense to change the notification scheme for your projects. Use caution when making these changes since Notification Schemes are typically shared across projects. Have a conversation with your team to ensure important information will not be missed if these settings are updated.
By following the steps above, you should have a lot more control of Jira emails coming your way. Notifications will now be for the tickets you care to follow or comments where you have been @ mentioned. Once you have your notifications under control, you can explore other ways to get your notifications such as in Slack. If you want to get really fancy, with the help of your Jira Administrator you can add custom event notifications, webhooks, and much more.
In addition to the tips mentioned in this article, if your team is using Jira Server or Data Center, when you upgrade to Jira 8 you can take advantage of Batched Email Notifications.
Chris Nicosia -Modus Create-
...steemed Steve Elliot (head of product for Jira Align). Agenda: What’s new or changed in SAFe 5.0: Introduction of OKRs Essential SAFe How to achieve true business a...
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