We have developped this feature in our company.
Perhaps this feature asks for a new role permission.

If the community is interrested in it, we will provide a patch.
--------------------------------------------------------------------------------
I'd be very interested in that - we came up with that same idea for a solution to the main Redmine issue we are having.

We have been running with Redmine for about a month and we really like getting all the conversations out of email (where they used to be) and into Redmine where they are centralized and searchable. However, to do that we have to have email notifications on, but far too many of the messages from the system are not interesting to most users and as a result, they may miss the important ones. If we could have the sender decide when they want others to see an issue update on a update by update basis, it would greatly improve the signal to noise ratio.

If you can send the patch, we'd definitely take a look at it.

Thanks
--------------------------------------------------------------------------------
I'd appreciate this patch very much. Please upload it.
--------------------------------------------------------------------------------
Hi, we add no time to develop the plugin.

But you should look this plugin that works very well :
https://github.com/teleological/redmine_stealth
--------------------------------------------------------------------------------
Redmine stealth is great but this should really be part of Redmine itself.

It would be way more practical that with adequate permission there is a [Submit Without Notifications] button when editing issues, along with global notification turn on/off. 2 cases of usage would be covered:

* Batch update of number of issues in stealth mode - this is now possible with redmine stealth. Also, it would be good to have [disable notifcations for N minutes] - when my admins are in the batch mode they frequently forget to turn notifications on after they finish.
* Acute update of one issue (setting little stuff such as correcting typos, adding issue category and other little things that may not deserve notification spam)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
-1
I am against this feature. With this feature, a user can secretly update issues without noticing watchers. I think this is a big problem.
--------------------------------------------------------------------------------
Hi,

* This is a common case in our company, when you don't want to bother users when cleaning issues for exemple.
* What is an issue for you ? that modifications are made without notifications ?
Perhaps we could add a mention in the issue update detail, to indicate that it was not notified to users ?
* The redmine_stealth plugin in one of this forks adds a new permission to decide who can disable notifications, we can perhaps use this idea :
https://github.com/Restream/redmine_stealth
--------------------------------------------------------------------------------
Jérôme BATAILLE wrote:
> * What is an issue for you ? that modifications are made without notifications ?

Yes.

A user watches objects to receive *all* notifications. Temporarily disabling notifications by a user who updates the object is not assumed or intended by the watcher. With the proposed feature, they cannot receive some notifications in spite of their intent.

It should be the watcher, not the user who updates objects, that controls what notification to receive.
--------------------------------------------------------------------------------
Hi,

I agree with your point of view, because Notifications are really important in the general case.
But some modifications do not need to bother all members of the project, for example :
* Fixing a typo
* Changing some Custom Field values that do not imply an action from the project members
* Changing issues in batch mode in some cases

And for these cases only a human can decide if it's necessary to bother project members with notifications.
If it's a real issue for some Companies environments, the permission to change an issue without notification could be given to a restricted list of roles.

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

relates,New,8409,single email for bulk updates
relates,New,5798,Bulk Notification Update or Combing Bulk Update Notification into one Email
relates,New,9482,Wiki - minor change without notification
relates,New,15928,Disable email notifications for ticket's updates
duplicates,Closed,14470,Standard implementation of redmine 'stealth mode'