Ticket #869 recorded.

1) what is the etc... ?

2) Pay attention that these mails may lead to real spamming.
For instance, mail on description change : when I prepare my ticket, I enter brief description. Then I complete it, and save several times. An email on each "description change" will be a mess.
The same for result : developer working on item should progressively complete result. Email on each change should be spamming. What is important in this case is the status change (when done is complete).

I just had development meeting and we have discussed that - I have highlighted that it can be spamming but developers said they need this to know what is going on...
etc. means that some other people may think about some other events...
Regards,
Evgueni

Any progress on that?
Say, on requirements change is extremely important because after that change test cases may be not valid anymore!
Regards,
Evgueni

Hi,

Ticket #908 recorded.
I noted :
- on notes change,
- on description change
- on result change
- on any change (personally I will never use this one !!!)

Any other idea ?

An idea

In the parameters (of email or event management): implement checkboxes so that everyone can select the events for which it would trigger an e-mail.

Cordially

Well, something like this is planned but not so restrictive.

Ticekt # 194 : don't receive team email : means if emails is sent to the team, just avoid it.

But I think this should not ne generalized too much.
When project leader (or admin) defines that an email must be send, for instance, on responsible change, team member should not go against this decision : he must receive the email.

I think this is enough
Thanks

Hi you 2,

I confirm this would be fine for us as well.

Klaus