what is the notification hierarchy in a Software Project Type (reporter vs assignee vs watcher)?

[Rosa M Fossi]

Hello Community,
I'm trying to figure out which notifications apply and in what order (if any?) when an user is reporter&watcher&assignee or any combination of those three (in a software development project). 

In our environment:
REPORTER: VERY few notifications; issue created, commented and resolved. 
ASSIGNEE:  few notifications; issue created, assigned, commented, reopened, moved.
WATCHER: most notifications; issue updated, resolved, commented, moved, generic. 

Most common scenario is Dev User opens a ticket, and then assigns the ticket to themselves.   That makes them the reporter AND assignee.    Will they receive notifications for everything that applies to reporter AND assignee?  And if they want to receive more notifications they could add themselves as watchers?

[Nic Brough -Adaptavist- · Accepted solution]

There is no heirarchy.

Let's say you've set up a scheme that sends to all three of those sets of people.  If a person is one of those three, they get included in the email.  If they are in 2 or 3 of those sets, they get included, but Jira de-duplicates so they don't get 2 or 3 emails.