Managing email notifications is not intuitive. Email notifications are without a doubt, overwhelming as they are issued for every, every, every little thing. Freedcamp generates way too many notifications.

Notifications go out for change of status, for change of assignment and so on, yet it is not crystal clear in the email that gets received as to why exactly the notification is issued because the notification contains the entire task -- task headers and entire comment thread. My clients hate the email notifications and therefore disregard them completely. I have setup Gmail filters to essentially send all/any incoming Freedcamp messages to trash because I cannot figure out how to effectively setup and manage them. This hiders project progress and effective communication tremendously.

If I want to add a comment without bombarding my clients, I must first uncheck the notifications checkbox for each client name; then post my comment; then check the notification box again to keep them on the task.

It would be great if the notifications service provided the ability to:
• select whether a notification should be issued or not when posting a comment,
• identify exactly and only what was changed – i.e., status was changed or assignment was changed, etc.
• if a notification goes out for a new comment, only send the new comment – don’t repeat the entire task thread all over again