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

Notification not being sent when a new comment is added via email using the MS Outlook client

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

      Summary

      When replying to a notification of a specific JIRA issue with Microsoft Outlook or adding a comment through email, a comment is added to the issue, but no notifications are sent to the watchers when the notification scheme is configured properly.

      Steps to Reproduce

      With Outlook
      1. Create a mail handler to a specific project
      2. In Issue Commented (Notification Scheme), add a notification to All Watchers
      3. Create an issue
      4. Ensure to set a few users as watchers
      5. Send an email out to JIRA's mail handler with the issue key of the step 3
      6. A comment is added to the issue
      7. No notifications are sent
      8. The log files (atlassian-jira-outgoing) show noting even with debug

      Expected Behavior

      The watchers should receive the notifications properly 

      Workaround

      Use the web client

            [JRASERVER-63582] Notification not being sent when a new comment is added via email using the MS Outlook client

            It looks like there may have been a fix for this implemented for ondemand users per https://jira.atlassian.com/browse/JRA-63694  Is there a fix for on-prem as well?  If not, it would be nice if this received the same attention. 

            Mark Holman added a comment - It looks like there may have been a fix for this implemented for ondemand users per https://jira.atlassian.com/browse/JRA-63694   Is there a fix for on-prem as well?  If not, it would be nice if this received the same attention. 

            This is far more important than a Medium issue.  This is a blocker/critical/firm breaking.  

            We can no longer count on JIRA to help us run our business.  The business workflows we have built for our firm are now broken, and we will move many of them away from JIRA since JIRA cloud is no longer dependable.

            This is a crucial bug of enormous import.  

            David McIntyre added a comment - This is far more important than a Medium issue.  This is a blocker/critical/firm breaking.   We can no longer count on JIRA to help us run our business.  The business workflows we have built for our firm are now broken, and we will move many of them away from JIRA since JIRA cloud is no longer dependable. This is a crucial bug of enormous import.  

            Update:

            We tested using Outlook 2013 and experienced the same issue.  As far as we can tell this started happening once we upgraded to 7.2.  We were on 6.x previously.

            Mark Holman added a comment - Update: We tested using Outlook 2013 and experienced the same issue.  As far as we can tell this started happening once we upgraded to 7.2.  We were on 6.x previously.

            IT Support added a comment -

            A few other important things to note:

            1. If when replying from Outlook you delete all of the old content in the body of the message and just include your new text, then the watchers receive the email as expected.
            2. This is with Outlook Version: 16.0.6965.2105.  We have not tested with previous releases of Outlook.
            3. Replying from Outlook Web and leaving all the old content in the body, the watchers are notified as expected.

            IT Support added a comment - A few other important things to note: If when replying from Outlook you delete all of the old content in the body of the message and just include your new text, then the watchers receive the email as expected. This is with Outlook Version: 16.0.6965.2105.  We have not tested with previous releases of Outlook. Replying from Outlook Web and leaving all the old content in the body, the watchers are notified as expected.

              Unassigned Unassigned
              pahennig Paulo Hennig (Inactive)
              Affected customers:
              10 This affects my team
              Watchers:
              17 Start watching this issue

                Created:
                Updated: