Redmine

1. It is not the same problem as in #21260, because I am talking about a user, who IS a member of the project.
2. It is much more like patch #16133, which I agree with (The proposed watchers on the new issue form should be able to at least view issues. Otherwise it would not make sense to add them as watchers.)

And I also add here: Even if the watcher IS member of the project!?!

1. It might by more like feature #13512, but I would not say it is a feature request, because the feature 'to add a watcher' is already there, but the watcher may not see the watched issue, until having a role permission, which gives him an access to that issue anyway.
2. Patch #14318 could be the right solution, but it does not make a sense completely to me to use new role permission for this, as a watcher should watch (read) the issue only not depending on his roles in project.

Thanks for understanding.

User "londruj" can only see "Issues created or assigned to user", so being watcher of the issue doesn't give him access (and if user can't access issue, he doesn't get email, so behaviour of Redmine seems OK).
Maybe related to #8488?

See also Go MAEDA's comment in #8488#note-159:

The following is Jean-Phillippe Lang's comment from #7412#note-13:

watchers were designed for notification purpose only. A user who unwatches a private issue would lost access to it. It may be quite confusing for many users.

Thanks a lot for commenting on that, I am aware of the fact, that watching does not give access to an issue. The problem in our situation is, that the user gets no notification email at all. Moreover, what sense does it make to be a watcher, when you can not watch? :-)
I have also read the #8488 and we will probably try the allow_watchers_and_contributers_access_to_issues_3.2.0 patch as soon as we find out, how to do it properly. Thanks again.

Hi again, I have double-checked this behaviour in version 3.3.1 too. Is it a chance to confirm this issue? Thanks.

I still think SEEING the issue and being NOTIFIED on issue updates are two completely separate things. Being able to add the issue creator (via e-mail) as a watcher for him/her to receive notifications that something has changed/happened on the issue that he/she reported is quite vital. Whether or not he/she should be able to see the issue is a separate matter.

Well, I see the difference between SEE and BE NOTIFIED, no doubt. What is the expected behaviour? To see (might be expected, when the verb WATCH was used), or get notified?

Milan Brabec wrote:

Well, I see the difference between SEE and BE NOTIFIED, no doubt. What is the expected behaviour? To see (might be expected, when the verb WATCH was used), or get notified?

Hi Milan,
I am experiencing the same problem with watchers that you reported some time ago. Did you manage to make watchers be able to see the issues?.I found the allow_watchers_and_contributers_access_to_issues_3.2.0 patch but could not be able to install it.

Did you find out how to do it?

Thanks in advance.

Hi Lara, I have succeeded with following patch:
23546-watched_or_created_or_assigned_issue_visibility.patch
Using this one, the watchers have access to watched issues, but certain setup is required after applying the patch.
I have created a new role "Watcher" with some explicit permissions for issues (like view issues, add/edit comments) and used "Issues watched by, created by or assigned to the user" in visibility section.