Comment 16 for bug 494257

The branch attached to this bug is finished, qa-ok, and released. The part that was qa-bad was fixed in a related branch that was a security fix, so I didn't comment initially when that the work was done. I was just marking a group of bugs fix released and not paying much attention to the bugs.

The initial problem was that the notify call that generates the activity/email was done from browser code not model code, and the API calls are based on the model. So the js subscribe-someone-else widget wasn't hitting the notify call. My branch for this bug did the work to move all this to model code. That is done, tested, and deployed. There is still bug 571821 to do, which is an easy fix to call Bug.subscribe with the new parameter. I just haven't got to it yet, but I'll do it this week and notifications should appear again. Once 571821 is fixed, this bug can be closed.