Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-41226

Comments From Email Trigger Notifications for "Issue Updated" Instead of "Issue Commented" Event

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Summary

      In the notification scheme, no one is set to receive Issue Updated, but users are set to receive Issue Commented. When a comment is added via email, nobody gets notification. When a comment is added via UI, they get notification for Issue Commented.

      After some testing I found that commenting via email will trigger Issue Updated, that is the reason users don't receive notification even though they are supposed to receive for Issue Commented. By right commenting via email and UI should behave the same and trigger Issue Commented and users should get notification.

      Steps to reproduce

      1. Install JIRA
      2. Configure Incoming Mail Handler (Create a new issue or add a comment to an existing issue) and Outgoing Mail
      3. Remove everyone from Issue Updated event but make sure they receive notifications from Issue Commented event
      4. Have a user add a comment to a particular issue via email

      Expected Results

      1. Comment added successfully
      2. Designated users receive notification
      3. Notification sent with Issue Commented event

      Actual Results

      1. Comment added successfully
      2. No notification received by users who supposed to receive Issue Commented event

      Notes

      • When the users are configured to receive notification from Issue Updated event, then commenting via email will send notifications to the designated users
      • Affecting with JIRA 6.3.10 and 6.3.12
      • With 6.2.7, notification will be of Issue Commented event (intended behavior)

            [JRASERVER-41226] Comments From Email Trigger Notifications for "Issue Updated" Instead of "Issue Commented" Event

            Hi all / andrea.turati / evangelos.vrocharis / andistuttgart / dl-vendors,

            This is a resolved issue, and as far as we know, it has not regressed.

            Consequently, I heavily suspect that you are observing a related but different problem in your instance. In order to be able to help you further, could you please get in touch with us via a support ticket at https://support.atlassian.com so we can look further into the particular problems in your instances.

            Furthermore, resolved issues are not actively triaged. If you think you are being affected via a resolved issue, please do get in touch with us at https://support.atlassian.com so we can help and confirm what is happening.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi all / andrea.turati / evangelos.vrocharis / andistuttgart / dl-vendors , This is a resolved issue, and as far as we know, it has not regressed. Consequently, I heavily suspect that you are observing a related but different problem in your instance. In order to be able to help you further, could you please get in touch with us via a support ticket at https://support.atlassian.com so we can look further into the particular problems in your instances. Furthermore, resolved issues are not actively triaged. If you think you are being affected via a resolved issue, please do get in touch with us at https://support.atlassian.com so we can help and confirm what is happening. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            We just upgraded to Jira 6.4.8 and this issue still persists. Email replies to issues still trigger issue updated event, instead of issue comment.

            Anyone know a workaround or what files need to be changed to trigger the correct event?

            HyTrust Admin added a comment - We just upgraded to Jira 6.4.8 and this issue still persists. Email replies to issues still trigger issue updated event, instead of issue comment. Anyone know a workaround or what files need to be changed to trigger the correct event?

            Andi Kuhn added a comment -

            Indeed we have the same Problem using 6.4.2 - Issue Commented is not triggered for Comments created by EMail Handler

            Andi Kuhn added a comment - Indeed we have the same Problem using 6.4.2 - Issue Commented is not triggered for Comments created by EMail Handler

            That's disappointing to hear, can someone confirm if this needs to be reopened?

            Evangelos Vrocharis added a comment - That's disappointing to hear, can someone confirm if this needs to be reopened?

            AT added a comment -

            We have updated JIRA to version 6.4.6 but the problem still remains.

            AT added a comment - We have updated JIRA to version 6.4.6 but the problem still remains.

            Hi evangelos.vrocharis,

            My previous comment refers to the original description of the issue which was not clear. This has since been corrected and my previous comment is no longer relevant I will remove it now.

            Sorry for any confusion,

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi evangelos.vrocharis , My previous comment refers to the original description of the issue which was not clear. This has since been corrected and my previous comment is no longer relevant I will remove it now. Sorry for any confusion, Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            There is a similar problem when adding a comment at the same time as attaching a file. It sucks, as 'Issue Updated' is far too broad, and results in users being spammed.

            The ideal fixes are to make emailed comments trigger 'Issue Commented' and add a new 'File attached' trigger too.

            David Turnbull added a comment - There is a similar problem when adding a comment at the same time as attaching a file. It sucks, as 'Issue Updated' is far too broad, and results in users being spammed. The ideal fixes are to make emailed comments trigger 'Issue Commented' and add a new 'File attached' trigger too.

            Evangelos Vrocharis added a comment - - edited

            -Oswaldo Hernandez's answer above makes no sense to me.

            The problem here is that when adding a comment via email an issue updated event is fired instead of issue commented. Unless that is intended for some reason, it's a bug and a pretty annoying one at that as Nick explained above.-

            Oswaldo's comment was obsolete so ignore this

            Evangelos Vrocharis added a comment - - edited -Oswaldo Hernandez's answer above makes no sense to me. The problem here is that when adding a comment via email an issue updated event is fired instead of issue commented. Unless that is intended for some reason, it's a bug and a pretty annoying one at that as Nick explained above.- Oswaldo's comment was obsolete so ignore this

            Hi there,
            Just thought I'd chime in and comment to hopefully up the priority on this. We intentionally removed notifications from the "Issue Updated" event in our initial deployment (August, '14) as our users found these notifications to be cumbersome and not very helpful. We've now added the appropriate recipients to this event in the notification scheme so our technicians will be notified when a customer replies back to an issue (which happens at least 90% of the time, email is the preferred way to communicate vs. the Service Desk customer portal or JIRA interface). Having this bug fixed so we could remove the workaround would be greatly appreciated by our users.

            Thanks,
            Nick

            Nick Ragusa added a comment - Hi there, Just thought I'd chime in and comment to hopefully up the priority on this. We intentionally removed notifications from the "Issue Updated" event in our initial deployment (August, '14) as our users found these notifications to be cumbersome and not very helpful. We've now added the appropriate recipients to this event in the notification scheme so our technicians will be notified when a customer replies back to an issue (which happens at least 90% of the time, email is the preferred way to communicate vs. the Service Desk customer portal or JIRA interface). Having this bug fixed so we could remove the workaround would be greatly appreciated by our users. Thanks, Nick

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              ywoo Yit Wei
              Affected customers:
              5 This affects my team
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: