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

Default mail handler prevents issue from being created if Forward Email is set

      Summary

      The default "Comments from emails" mail handler prevents an issue from being created if a Forward Email is set and the said mail handler comes first in the list of Mail Handlers at the IncomingMailServers section in Jira:

      • https://<instance>.atlassian.net/secure/admin/IncomingMailServers.jspa

      Steps to Reproduce

      1. Have a setup like this:
      2. Edit the first mail handler to switch its position to make sure the default Comments from emails process the message first:
      3. Set a fwd email address to the Comments from emails mail handler.

      Expected Results

      The message will be first processed by the Comments from emails mail handler, which will throw the following error in logs:

      Comments from emails - Cannot handle message as destination project has not been configured.

      If there isn't any forward email address set, the next mail handler will attempt to process the message, which will most likely succeed, and the following logs will show up:

      Create Issue - SOUP - Issue SOUP-14 created 	 	 
      Create Issue - SOUP - No Issue found for email 'A new test email ' - creating a new Issue. 	 	 
      Create Issue - SOUP - Issue Key not found in subject 'A new test email'. Inspecting the in-reply-to message ID. 

      Actual Results

      If a fwd email is in play, the message will not be processed by the second mail handler in the list.

            [JRACLOUD-76462] Default mail handler prevents issue from being created if Forward Email is set

            Atlassian Update - August 7, 2024

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - August 7, 2024 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              epereira@atlassian.com bpevandro (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: