Notification platform adds `bulk` header by default irrespective of the General Settings on Jira Cloud Sites

XMLWordPrintable

    • 3
    • Severity 3 - Minor

      Issue Summary

      Notification platform adds precedence `bulk` header by default irrespective of the General Settings on a Jira Cloud site
      .

      Steps to Reproduce

      1. Navigate to General Settings on your Jira Site: secure/admin/ViewApplicationProperties.jspa
      2. Click on the Edit Settings option to edit the "Exclude email header
        "Precedence: bulk" option and set it to ON. (This updates JIRA Notification Platform whether to exclude the 'Precedence: bulk' header on Jira notification emails or not).

      Expected Results

      Based on the General Settings, If the Setting is toggled ON, then the 'Bulk' precedence should be excluded from the email header, and if it is toggled OFF then where appropriate the 'Bulk' precedence should be set on the email header.

      Actual Results

      Regardless of the setting being ON or OFF the precedence 'Bulk' is always set in the outgoing emails from JIRA.

      Workaround

      • As per recent updates, we have found that changing the "Email Notification Format" to TEXT from the Personal Settings page URL: secure/ViewPersonalSettings.jspa can avoid the discrepancy in the email header. However, if it's set to HTML the precedence set under General Setting is not obeyed by the Notification Platform.

      There has been recent planning and development happening on this where the product team has decided to move to a different notification platform. This BUG would be fixed as part of our current development plan where we are going to migrate from the notification platform to Atlassian Mail.

      We do not have a defined ETA for this, but we will update this ticket when we have more information on the same.

              Assignee:
              Vivek Manohar (Inactive)
              Reporter:
              Vaibhav Revankar
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: