Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-44680

Issues created via email when catch mail specified in BCC fail to be created

    XMLWordPrintable

Details

    Description

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

      Issue Summary:

      When a user specifies an email in the catch email and sends in an email with the specified email in the catch section added into BCC field of the email that is being sent to JIRA.

      An issue would not be created, despite the catch email being added to one of the fields mentioned.

      If specified, only email messages whose To:, Cc:, Bcc: lines contain the recipient specified in this field will be processed — for example, issues@mycompany.com

      Upon specifying an address here, all email messages whose To:, Cc:, Bcc: lines contain addresses other than the Catch Email Address are ignored. This is useful if you have multiple aliases for the same mail account (e.g. foo-support@example-co.com and bar-support@example-co.com aliases for support@example-co.com) for multiple mail services (e.g. each one to create issues in separate JIRA projects).

      (info) Note: in practice, this option is rarely useful and should not be confused with the more common Default Reporter. You can only specify one catch email address and one issue type per mail handler.

      Steps to reproduce:

      • Configuring an incoming mail handler.
      • Add in the catch email.
      • Create an issue via email adding in the specified catch email to the BCC field.
      • Send the email and check if an issue is created.

      Expected Result

      • Issue is created in JIRA

      Actual Result

      • No Issue is created

      Error in Logs

      Cannot handle message.  No recipient addresses found.
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              ijimoh Ismael Olusula Jimoh (Inactive)
              Votes:
              6 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: