Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-41831

Duplicate issues creation fails - Creating multiple issues by one Email

    XMLWordPrintable

    Details

      Description

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

      Summary

      Creating issues with one mail to 3 different addresses fails in JIRA 6.3 and 6.4
      When we have 3 different mail handlers and each one of them associating with a different project:

      • Mail Handler 1 --> Project 1
      • Mail Handler 2 --> Project 2
      • Mail Handler 3 --> Project 3

      Steps to Reproduce

      1. Create 3 projects
      2. Associate one mail handler to each project
      3. Create one Email and having 3 mail handlers in "TO" field
      4. Send

      Expected Results

      Since we have 3 mail handlers 3 issues with same summary and description should be created in 3 different projects.

      Actual Results

      It has been tested in version 6.0.8 and the issues can be created, but in versions 6.3.x and 6.4.x, the issues being created randomly in different projects.

      The following error has been found in the test instance and the customer's JIRA instance:

      2015-01-28 14:28:52,060 WARN [Test1] atlassian-scheduler-quartz1.clustered_Worker-1 ServiceRunner    Testone Testone[10300]: Deleting message 'David Currie - order 1 2 3' without processing in order to avoid creating duplicate issues/comments. This message has already been partially processed, associated issue key: EMTHREE-6
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              Reporter:
              somidi Sam Omidi (Inactive)
              Votes:
              38 Vote for this issue
              Watchers:
              41 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: