• I don't have to maintain external mailing lists or mail aliases for group notification

Covered notifications:

• In tracker, "Global notification" defined by tracker administrator
• In git, "Notification" per repository defined by git administrator
• In docman, "Notification" per doc/folder defined by docman manager

Excluded:

• Tracker filed "CC" (open list) as they already managed groups
• SVN Plugin, need a redesign of notifications, will be covered in a dedicated story
• SVN Core and CVS: legacy, won't be covered.

Behaviour

Changes:

• New autocompleter to either pick from users or groups
• New, consistent, display of notifications as a table
• Storage of notified items will now favor users or groups over email addresses
  • emails can still be used but we won't convert a username to an email when we add a new notification.
• On send of emails:
  • Emails are deduplicated (given John is part of Developer group and notified individually, he will receive only one message)
  • Permissions apply for groups as they apply for individual

Technical side

• Autocompleter based on select2 componenet
• Ajax route to return users and groups (/!\ LDAP)
• Backend
  • 2 new tables to store user and groups association
  • Existing notifications are not changed and assumed as "email" notif
• Display
  • Build table with various notification types + ability to remove
• On send
  • De-duplicate emails (user, groups, email)
  • Ensure email sending validation & filter applies

Special care should be taken to edge cases:

• When project are removed
• When user groups are removed