Any way to tweak Jira notifications? Especially for a manager they are bad...

[Amir Colnect]

There's an inherent problem with managing notifications on Jira projects. As a manager, it's enough for me to know there are notifications on an issue and once I review it and attend to it, I should have a way to mark that the issue isn't of further interest to me. But:
1/ In the notification popup on site I would still see previous (sometimes A LOT) notifications about the issue which I've just attended to and have to mark each one separately as read.
2/ In emails, it would make sense for me to NOT get further emails about an issue while I haven't reviewed it. This should be optional. Many message boards/forums do that when they send you one email about an update to a topic you're following but now dozens as more people keep responding.

Is this at all possible on Jira?

UPDATE: seems not :(

[Daniel Ebers]

Hi @Amir Colnect

yes, this is a common topic and like Jack suggested one option would be to tune the notification schemes to improve the situation.

What many users find coming in handy is to have a filter subscription for their teams - in other words a digest of what happened lately, based on a JQL query:

• JQL: Using filters and subscriptions
  https://www.atlassian.com/blog/jira-software/jql-the-most-flexible-way-to-search-jira-3-of-4

Doing so, in several cases users could reduce amount of mails being sent how it was defined in Notification Schemes.

One team that I spoke lately now relies on dashboards. This however needs a good discipline to look into Jira (almost) every day, as they obviously now do not receive mails for issue notifications anymore.

Cheers,
Daniel

[Amir Colnect]

Thank you for taking your time Daniel but neither in the answer nor the link could I find anything that would solve the issue I mention. "To improve the situation" by choosing some notification scheme, doesn't seem to me like something that would solve a fairly common (correct me if wrong) missing feature. Is there an actual way to not receive further notifications for an issue once there's an unread notification about it?

[Daniel Ebers]

Yes, you are much right - the notifications are not a match for all users.
I just read about some upcoming improvements, even this would also not be an exact match to your environment it could be worth having a short read.

https://community.atlassian.com/t5/Feedback-Forum-articles/Improving-the-way-you-manage-notifications/ba-p/1720859

In general, I think, there are improvements upcoming which is a good sign.
However, not every specific need is yet addressed, I fully agree with you.

[Amir Colnect]

When, I'd expect my use case to actually be a very common one. I doubt anyone needs to see a dozen notifications about the same item... They just go into the issue and review the changes.

Thanks for the link

[Jack Brickey]

The notifications you receive are influenced by many factors. First and most importantly they are managed by the notification scheme. There are various events that occur such as issue created issue commented issue transition and so forth that can be set to issue notifications to various individuals groups or roles. Secondly it will depend on the role you play on an issue. For example you might be a reporter or you might be a watcher or you might be an assignee. So now hell you a dress the notifications you receive will depend on those many factors. For example let’s say that you are not the reporter or the assignee but simply a watcher. In that case will you become an interested with further updates then you can simply stop watching the issue. However if you are the reporter then that will be entirely controlled by the notification scheme and you’ll need to look at that notification scheme to understand when you will receive notifications and consider making changes to reduce or eliminate notifications.

[Amir Colnect]

I thank you for your reply but I don't believe it addresses the issue I'm raising. I'll give an example. Say I'm the reporter in a Jira issue and so want to receive notifications about it. There could be some developers and testers interacting with it and they may add comments. Sometimes there could be many comments every day. For me, it'll be enough to receive a single notification about that issue but no further notifications until I actually visit that issue as when I go there once, I'll review all the previous things that have happened and choose if I need to do anything about it. Currently, I'll easily see a dozen notifications for the same issue and in 

1/ Activity feed - each notification is separate and I can't get rid of all notifications for that issue in a single click but have to click on each and every one.

2/ Emails - I keep getting emails for each notification and I'd be better off seeing a single email and not more.

Is this something which can be achieved?