The goal of the feature is to bring the, now ubiquitous, (email) notification when using @username in a Tuleap where it's relevant. This is a one time notification, the user who's being notified won't receive updates for future notifications.

The introduction of this feature, esp. in Trackers, leads to a lot of questions regarding Notifications at large. The default mode of Tuleap as of today is rather verbose, a lot of emails are sent. A lot of people, esp. new users, complains about the amount of emails they receive from Tuleap. This lead to an ever growing set of options to limit the amount of emails (emails only at creation, only on status change, no email when for the author of a change, ...). Due to the different natures of the configuration (personal, per tracker, user based, tracker bases), the configuration is utterly complex to understand and to debug.

There is an opportunity to re-define the way notification works with this goal:

• Defaults should match what most people expect nowadays (2024)
• We should aim to keep current users un-affected of this change to avoid breaking existing use case
• We should aim to provide current users who want to keep their inbox lean a clear path to Modern email configuration

What should be the new default ?

• Author of a change should not receive an email for the action they did, unless they explicitly opted-in
• One time comment should not imply receiving email for all future updates, unless they explicitly opted-in

In addition to new defaults, it should be possible to subscribe to a given artifact without having to setup a "CC field" and to let people add themselves to the CC list.