Disable auto-notifications for reporter?

As a reporter of a specific issue, I receive notifications for every update in the issue, although I am not watching the issue (it does give me the ability to start watching it).

Is there any way to prevent this from happening? Is it something that requires administrator privileges?

3 answers

1 accepted

1 vote
Accepted answer

It is mostly because the reporter is added into the notification scheme used by your project and not just watchers. Any changes to that can only be done by a JIRA admin.

Thanks! Straight to the point.

Are there specific instruction a JIRA admin can follow to modify the notification scheme to accomplish this?

 

Can you modify the notification scheme in such as way that it disables auto-notifications for some issues that someone is a reporter for but not others?

I wonder if this is a UX (user experience) issue that needs fixing, rather than a technical issue?

Perhaps the user interface needs to adhere to this mental model:

WHEN I (a Jira user) click 'Stop watching' on a Jira issue,
THEN I (a Jira user) stop receiving any e-mails and/or notifications about that issue. 

Which differs from the system designer's model of adhering to notification schemes (which are only editable by a system administrator).

Supporting evidence user's perceive this as a problem:

Supporting academic reference(s) for the hypothesis:

-

Anecdotally, I have experienced this issue in a couple of workplaces on many projects, and, in my experience, in response to this UX issue, users tend to:

  • ignore/hide/disable all Jira notifications
  • stop commenting on Jira tickets
  • use other ways of communicating with the team that have the disadvantage of not being tied to a Jira issue number by default

The broken approach is that there are two methods driving notifications for an issue: the Notification Scheme for the project and the Watchers system.

This should be simplified so that there is only one system (the Watchers system) and the project-level configuration should come down to who should be added automatically to the watchers list.

Then, when it is no longer appropriate for a user to be notified of changes to an issue, this can be managed on an issue-by-issue basis by the user themselves or an admin with the Manage Watchers privilege.

 

Recommendations here and elsewhere to:

  • change the reporter, either automatically or manually
  • change the notification scheme

are invalid: changing the reporter loses important information (or hides it, at least) - it might well be useful to know whom to contact for more information on an issue; changing the notification scheme across the project is too wide an impact for something that should be manageable by individual users on an issue-by-issue basis.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,173 views 5 10
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you