Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
The Plugin People
Teams
, (opens new window)
Knowledge Base
  • How-to articles
    How-to articles
     This trigger is hidden
Results will update as you type.
  • Enterprise Mail Handler - JEMH - (Server/DataCenter)
    • Auditing History purge does not work with "Retain Failures" enabled (JIRA 7.x)
    • Concurrent mail retrieval resulting in duplicate issue creation
    • Configuration screen won't save updates
    • Creating duplicate issues to multiple projects fails
    • Diagnosing Slow or Stopped Incoming Mail
    • Duplicate issues are created when using JEMH and JIRA Data Center
    • Email client shows encoded attachment name instead of decoded file name
    • Enable Auto Labelling
    • Event Listener JSD issue transition notifications do not send if a comment is present in the transition
    • Exception during issue update validation for non-Service Desk issue
    • File Attachments cause Out Of Memory problems
    • Gmail confidential mode
    • How to supply a default value for the Tempo Account custom field
    • How to support email addresses with international characters
    • Issue fails to create with indexing errors
    • JEMH Is not yet licensed through Atlassian Marketplace
    • JIRA fires Issue Assigned event for newly created Issues
    • Jira Service Desk problems
    • Jira 7 *Wrong JVM Version!* Error
    • JSD Organization field
    • Mail fails to be retrieved from mail server
    • MYSQL exception - Caused by: java.sql.SQLException: Incorrect string value
    • MYSQL Duplicate entry '0'. No Valid License
    • Non-JIRA recipient custom field values have been updated but JEMH is notifying the old values
    • Notification History tab does not show on issues
    • Problems with IMAP
    • Problems with POP
    • Slow Jira startup with PostgreSQL
    • Sorry, you can't create any issues right now, as you need to have access to a JIRA application to be able to create issues
    • You do not have permission to assign issues
    • How to change the event type of a notified event
    • Diagnose no inbound mail handled
    • JSD (Jira Service Desk) - Who is notified when?
    • HTML extraction method to Wiki mark up
    • Setting System Fields using Script Field Processor
    • Test case editor fails to load
    • MessageRemovedException in log files during email processing
    • Characters appearing as question marks
    • UI not visible after upgrading to version 3+
    • Default Project Mapping and unwanted inheritance causing inbound mail to be forwarded
    • JEMH is disabled on startup in Manage Apps
    • Configure JSD Customers for use with JEMH
    • Custom Field values are cached causing recipients to not receive notifications (JIRA 7.3.0 - 7.3.4 , JEMH 2.1.0 - 2.1.11)
    • Restrict commenting to one project
    Calendars
You‘re viewing this with anonymous access, so some content might be blocked.
/
Creating duplicate issues to multiple projects fails
Published Sept 08, 2017

    Creating duplicate issues to multiple projects fails

    Sept 08, 2017

    Problem

    In the scenario where you are sending one email to multiple addresses in order to create issues in multiple projects, JIRA fails to create all of the issues.  If Inbound Mail Logging is enabled, the following message will appear: 2015-11-04 14:27:33,512 WARN [PPL2Mailbox2] atlassian-scheduler-quartz1.clustered_Worker-1 ServiceRunner    Mailbox2 Mailbox2[10103]: Deleting message 'test issue subject line' without processing in order to avoid creating duplicate issues/comments. This message has already been partially processed, associated issue key: TEST-18

    Solution

    This is a known JIRA bug and may be fixed in a future version: https://jira.atlassian.com/browse/JRA-41831 Duplicate issues creation fails - Creating multiple issues by one Email.

    Related articles

    • Page:
      Diagnose no inbound mail handled
    • Page:
      JSD Organization field
    • Page:
      How to supply a default value for the Tempo Account custom field
    • Page:
      Enable Auto Labelling
    • Page:
      Jira's Inbound Mail Processing fails due to Basic Authentication Deprecation







    {"serverDuration": 18, "requestCorrelationId": "4f9270f5b02346b78f3ef177aacc472d"}