You can configure notification events in "Administration" > "Settings" > "Select actions for which email notifications should be sent.". In the section, you can see "Issue updated" and its sub-events, "Note added", "Status updated", "Assignee updated", and "Priority updated".

The issue I am going to point out is that the four sub-events don't cover all notification types that handled by the "Issue updated" event. For example, add/remove relations trigger notifications if "Issue updated" is enabled. But there is no such sub-event on the page.

As a result, the following two configurations work differently. I think most users expect that the two configurations work the same. It is confusing.

!{width: 370px; border: 1px solid #ccc;}.notified-events-config-1@2x.png!

!{width: 370px; border: 1px solid #ccc;}.notified-events-config-2@2x.png!

It is quite misleading. Many users misunderstand that "Issue updated" consists of "Note added", "Status updated", "Assignee updated", and " Priority updated". But "Issue updated" includes some other "hidden" events such as an update of description and a change of relation. Probably users never think that "Issue updated" includes "hidden" events.

My idea to resolve the problem is to add a new sub-event "Other issue attributes updated". This sub-event covers all other events (I mentioned before as "hidden events").

!{width: 380px; border: 1px solid #ccc;}.other-issue-attributes-event@2x.png!

The benefits of adding the sub-event as follows:

• Users can easily understand that there are some other events that trigger notifications
• It makes easy for users to find the way to disable unimportant notifications such as "Relation added"
• Makes things consistent. There are no "hidden" events any longer