Redmine

Can somebody point how do I debug this issue?
I am currently looking at the code but have no idea where to start looking at the code that is causing the issue.

Abdul Halim Mat Ali wrote:

Can this patch be integrated?

+1 to Abdul Halim

As far as I understand watchers are not notified of issues in private projects where they are non members because "if they unwatch the issue they loose any contact with the issue, and this may be confusing".

• this is exactly what happens to users that may only view issues assigned to them, and that are unassigned
• for my users it is much more confusing to be allowed to add watchers that are not notified, while they think they are!

I also know that watchers are intended just for notifications. But why? Is it meaningful to have notified something that is not visible?

(reasoning over 1.4.7)

Thanks

I think that actually this behavior generates confusion.

I have a watcher in an issue in a private project.

Without the patch he doesn't receive any notification about it.
Anyone looking the issue is having a wrong information, thinking he is receiving notifications.

So:

- remove the feature to add non project watchers to an issue
or
- integrate the patch

Thank you.

For your information, I have developed a plugin that solves the problem, compatible with Redmine 2.3.2: https://github.com/maxrossello/redmine_extended_watchers

There are two branches:
- in the master branch, watchers are enabled to view the issue (and the project) as long as they are watchers. There is no need to give any role to them into the project. They can interact with the issue in readonly, having just view permissions.
- in the 'with_view_own' branch, a watcher can be added only if he has at least the 'view own or assigned' permission. The issue visibility will be therefore much like that of an assigned user: a) the project is visible anyway, b) the issue is visible just as long as the user is assigned to the issue (in our case as long as he is set as a watcher)

One of the two strategies should be merged into Redmine trunk, I feel. Keeping the standard Redmine behavior was not an option in our company. People were expecting people to be notified while they were not.

Totally agree with Stefano and Massimo, I've been debugging this issue for days, a watcher should receive notifications, if not, it's not a watcher.

I just ran into this as well. I may not want a user to watch any ticket in a project. I just want to assign them as a watcher for a single issue and have them receive email notifications. As it is now, this was very confusing and I couldn't figure out what was wrong until I watched my postfix logs and saw redmine was only sending notifications to project members.

+1

Agreed that non-member watchers in private projects should receive email notifications. Currently there is no effect besides the option causing confusion.

+1

+1

+1

With this Feature enabled we'd be able to use Redmine as Ticket System and Support System, right now we are forced to send our customers emails manually which is not really nice. If anyone has a solution for that please inform me how.