ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Notification - Dont notify of changes I make is confusing (Feature #715)

Added by Brian Jacobi at 2011-11-17 10:55 pm. Updated at 2011-11-21 02:42 pm.

Status:Open Start date:2011-11-17
Priority:Normal Due date:
Assignee:- % Done:


Target version:-
Remote issue URL: Affected version:


Users who have this turned on don't realize that when a ticket is submitted and this box is checked, they will not receive an email. Emailed ticket submissions should always result in a response to a user unless no events are turned on.

Associated revisions

Revision b0bb41ad
Added by Jean-Philippe Lang at 2008-02-22 06:48 pm

Fixed: Issue custom fields "required" flag not stored (broken by r1090). Closes #715.

git-svn-id: e93f8b46-1217-0410-a6f0-8f06a7374b81


Updated by Holger Just at 2011-11-21 01:05 pm

Well, that option is exactly for this purpose (and is unchecked by default). Some people do actually not want to be notified for any changes they make. Issue creations are in no way special here. It would be very confusing for users intentionally checking this option to receive mails for their created issues. So as this stands, I'd decline this feature. I don't like arbitrary hard-coded exceptions to clear rules.

However, I think it would be good if (as a generalization) there was a way to configure which messages should be sent for each object type (with sane "templates"). This would bring the user back in command and would allow to configure their notifications very fine granular.

Updated by Brian Jacobi at 2011-11-21 02:42 pm

I'm okay with the later, having more granular notification would be best. Thanks Holger

Also available in: Atom PDF