|
History
| Log In
|
|
|
|
I just realized that the real underlying solution here is to make modification of the Watcher list to be an "update event", so that the current (not yet modified) Watcher list will be informed.
This has the added benefit that if if someone else adds you to the Watcher list, you can see who added you. Hopefully a simple fix? Anton, I did read through the cc list enhancement, and while it is related, that enhancement is asking for a lot more, mostly for the purpose of customization and adding watcher-like users through different means than are currently available.
So this bug seems to be a low-hanging fruit compared to that one. Then again, if I'm the first to complain about this, maybe most people don't find it to be a big deal. Lawrence,
Unfortunately the fruit is not hanging that low if you take into consideration how JIRA event system works. Currently the event system assumes that all notifictaions go to parties selected in the Notification Scheme for each event. This would be a 'special case' that does not fit into the box. Cheers, Hi Anton, is your comment assuming that we want only the removed party to get notified?
If so, I don't think we'd need that; having all users who get notified for the "Issue Updated" event be updated in this case would be sufficient. For example, my JIRA is currently set up so that the "All Watchers" group (among others) is registered (in the default notification scheme) for the event "Issue Updated". All I really want here is for modifications to the Watcher list to be raised as ""Issue Updated" events, with the obvious info (this user changed the list, these users added, these removed). The only important thing is that the membership of the "All Watchers" group be resolved before the change, or else have it take into account the superset of the two lists. I would imagine this same logic is in place when assignee is changed and the Current Assignee needs to be notified, as well as the new assignee. If I'm misunderstanding you, please clarify, thanks. That issue really hurts. I'm watching many issues in different JIRAs. If I won't be notified if someone removes me from any issue then is could be easily abused in some environments where my participation in a specific discussion is expected.
Gunnar, you could (via permission scheme) prevent anyone from managing the watcher list. that way you're the only one who could choose to Watch or Unwatch an issue. The logic is that if you have granted Manage watchers permission to someone, that you trust them not to abuse it. if you don't, they shouldn't have that permission. IMHO, that makes sense.
Thanks but this doesn't work. We try to follow an open development model and that requires that any developers should be able to invite other developers into a discussion and we don't want people sending emails outside of JIRA. Otherwise we would loose important information if communicated outside of JIRA.
OK, I hear you. Here's how I get around it. Essentially I have two ways to "watch" an issue. One is by using the built in Watch feature. The other is by adding yourself (or others) to a custom field called "cc to:". The notification scheme sends emails to All Watchers, and all users currently being cc'd. While anyone can edit the custom cc field (adding and removing users), no-one can remove someone from the watcher list. So, if you want to watch an issue and be sure you aren't removed, use the Watch issue feature and restrict the manage watcher permission. And if you want developers to invite others, use the cc feature. If you're on both, JIRA will only send you one email.
The cc method has an added benefit, because you can add a user as a 'watcher' at issue creation, which is currently not available (JRA-5493) I attached a screenshot to illustrate, and it's also explained at JRA-5493. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
A Watching user is not notified when they are removed from the Watcher list
You are right, the cc functionality does not work exactly the same as it does in Bugzilla. I have linked this request to the main improvment.
Thanks,
Anton