Mantis Bug Tracker - Forums

I am having a strange problem with email notifications for new bug notes. I assume there is a setting somewhere starring me in the face that I just can't see for some reason so if someone could help me out I would really appreciate it.

My specific problem seems to be related to one user who is an admin on the project (but not the system as a whole). Whenever she adds a bug note the system doesn't send any emails but whenever anyone else adds a bug note the system does send emails. Emails are also generated whenever she assigns a ticket. As far as I know the only user option is whether they want to receive emails and not if they want to send them. The system is configured to send emails for new bug notes and as I mentioned it does work for other users.

I checked the email log and while there are many lines like this for when others add notes:

2016-11-16 09:44 EST mail_recipient Issue = #13708, add Handler = @U142
2016-11-16 09:45 EST mail_recipient Issue = #13708, add Reporter = @U142
2016-11-16 09:45 EST mail_recipient Issue = #13708, add Handler = @U142
2016-11-16 09:45 EST mail_recipient Issue = #13708, add Note Author = @U285
2016-11-16 09:45 EST mail_recipient Issue = #13708, drop @U285 (own)

There is no email sent when this one user (@U142 in this case) creates a bug note. The email in this case should go to @U285. There aren't any lines in the log that that issue number at the time stamp the bug was added.

Is there a setting I am missing that would cause this?

The log tells that @U285 was the one who added the note and has been dropped as a recipient because users don't get notifications for their own activities.

Hi Atrol

Sorry but the way I worded it may have been confusing but the problem is still unsolved. The log I posted below:

2016-11-16 09:44 EST mail_recipient Issue = #13708, add Handler = @U142
2016-11-16 09:45 EST mail_recipient Issue = #13708, add Reporter = @U142
2016-11-16 09:45 EST mail_recipient Issue = #13708, add Handler = @U142
2016-11-16 09:45 EST mail_recipient Issue = #13708, add Note Author = @U285
2016-11-16 09:45 EST mail_recipient Issue = #13708, drop @U285 (own)

is an example of the email working. When @U285 creates a bug note, an email IS generated as you can see by the log info. The problem is that when @U142 creates a bug note in reply, an email is NOT generated. There is NOTHING in the log at all for the same timestamp as when the bug note was created. If an email was not going out due to user preferences I would expect it to say adding user(s) and then removing user(s) but its as if its ignoring that update altogether for some reason. Not to mention @U285 receives an email for bugnotes from all other users.

I've tried to reproduce with another user with similar permissions but I can't see to. Am I missing something?

Ok so it seems I've tracked it down.

If a user views a ticket and adds a note the emails are sent as expected.

If a user edits a ticket, enters text in the note field and selects "Update Information" then an email won't go out despite a bug note being added.

Is this standard behavior? Is there a way to get it to treat both as a new bug note and send an email?

I get a different email (bug has been updated) when using the update page.

Which version of MantisBT do you use?

Our version is a bit older 1.2.18 - I would update it but it will need to be a bit of a project because of some modifications we made including a plugin to a survey system we created.

Looking at the email notifications page I see these options:

E-mail on Change of Handler
E-mail on Reopened
E-mail on Deleted
E-mail on Note Added
E-mail on Relationship changed

I don't see anything for bug updated. Is this handled somewhere else or just not at all in my version?

There was a bug in 1.2.18 related to email notifications which has been fixed in 1.2.19.
https://www.mantisbt.org/bugs/view.php?id=17925

I don't have time to have a deeper look at it, so this might not be related to your issue.
I understand that you don't want to upgrade to latest stable version (1.3.3 at the moment), but upgrading to 1.2.19 (or run in parallel) should be no big deal.
There are no database schema changes in 1.2.19 compared to 1.2.18, so you don't have to run any upgrade script, but just use the files that come with 1.2.19.
You could anytime revert to 1.2.18 if you encounter a problem when using 1.2.19.

feesh wrote:because of some modifications we made including a plugin to a survey system we created.

Double check that your modifications and/or the plugin do not introduce the issue.

Thanks for your help!