Project: | The Hive project |
Component: | Project components |
Category: | bug report |
Priority: | normal |
Assigned: | jurjen |
Status: | closed |
When a visitor (specifically "ameijer") reports an issue, and someone else (like myself) creates a follow-up on that issue, for example to say that the issue is fixed and a patch is available, then I would expect that this visitor("ameijer" in this example) would receive an e-mail notification. But he does not get one. He only gets e-mail notifications for new comments(!) on the issue if he is subscribed to site-wide notifications for new comments.
That does not seem right to me. I assume that people are highly interested in follow-ups on their own issues.
Comments
Agree
Seems reasonable.
PSDN Model
FWIW, I am pretty happy with the PSDN model. In the user profile one can set yes or no for both "Watch all topics that I create" and "Watch all topics that I reply to" . Combined with the ability to explicitly watch any thread or forum, that pretty well covers the boat.
re PSDN model
So maybe we should add the subscriptions.module to the list of things to evaluate:
http://drupal.org/project/subscriptions (but it would not help with issue follow-ups, unless you add comment to an issue in addition to a follow-up)
What's it like, really?
A bit hard to tell from that link what it really looks like in use. Seems like an idea, though. If easy to use ... which is what I like about the PSDN model, which is both easy and very obvious and direct ... then it would seem like an attraction. I notice that it is one of those ready for 5.x, which seems to auger well for being maintained and current.
#1
found part of the solution: people have to submit this issue subscription form (for each project) if they want to get notifications:
http://www.oehive.org/project/issues/subscribe/hive.
Although it is not unreasonable to have a (un)subscription form, I think it is not exactly intiutive. Even I did not know until today that the form existed! I propose that a user who creates an issue (or even a follow-up) is automatically subscribed to "own issues" if he isn't already. Agree?
#2
Fixed, changed the code.
The person who creates an issue is now automatically subscribed and will receive email notifications for "own issues". The person who the issue is assigned to, too.
#3
For your information and amusement: the project leader at drupal.org didn't like my fix (see http://drupal.org/node/126774) but since we are only a small site compared to drupal.org I am going to keep my fix until he comes up with something better.