Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-30293

Duplicating issue when replying to e-mail

XMLWordPrintable

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

      When replying to an e-mail that was sent to create a JIRA issue, instead of adding a comment to the related issue, as it should according to this documentation, the reply e-mail is creating a new JIRA issue.
      As he does not find the JIRA Issue Key in the e-mail subject, he should check the in-reply-to header of the e-mail to see if the first e-mail of the chain created an issue, and it seems the system is not doing that.

      Steps to reproduce

      1. Send an e-mail to create and issue with a Cc to yourself or another e-mail.
        1. This e-mail has the example ID: 1234
      2. Wait for the issue to be created.
        1. JIRA replies with an e-mail that has the example ID: ABCD
      3. Now, using the CC address, just reply the email with ID: 1234 that created the issue.

      The handler is not following the In-reply-to ID.

      Expected behavior - The reply should be added as a comment to the issue.
      Actual behavior - The reply is creating a new issue. (Duplicated one)

            [JRASERVER-30293] Duplicating issue when replying to e-mail

            Julien Rey made changes -
            Assignee Original: Shiwani Choudhary [ 6f6f0ed1241f ] New: Eric Dalgliesh [ edalgliesh ]
            Shiwani Choudhary made changes -
            Assignee Original: Eric Dalgliesh [ edalgliesh ] New: Shiwani Choudhary [ 6f6f0ed1241f ]
            Bugfix Automation Bot made changes -
            Minimum Version New: 5.02
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2834052 ] New: JAC Bug Workflow v3 [ 2924314 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2591735 ] New: JAC Bug Workflow v2 [ 2834052 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1538640 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2591735 ]
            jonah (Inactive) made changes -
            Description Original: When replying to an e-mail that was sent to create a JIRA issue, instead of adding a comment to the related issue, as it should according to [this documentation|https://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email#CreatingIssuesandCommentsfromEmail-Issue/commentcreation], the reply e-mail is creating a new JIRA issue.
            As he does not find the JIRA Issue Key in the e-mail subject, he should check the in-reply-to header of the e-mail to see if the first e-mail of the chain created an issue, and it seems the system is not doing that.

            *Steps to reproduce*

            # Send an e-mail to create and issue with a Cc to yourself or another e-mail.
            ## This e-mail has the example ID: 1234
            # Wait for the issue to be created.
            ## JIRA replies with an e-mail that has the example ID: ABCD
            # Now, using the CC address, just reply the email with ID: 1234 that created the issue.

            The handler is not following the In-reply-to ID.

            Expected behavior - The reply should be added as a comment to the issue.
            Actual behavior - The reply is creating a new issue. (Duplicated one)             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRACLOUD-30293].
              {panel}

            When replying to an e-mail that was sent to create a JIRA issue, instead of adding a comment to the related issue, as it should according to [this documentation|https://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email#CreatingIssuesandCommentsfromEmail-Issue/commentcreation], the reply e-mail is creating a new JIRA issue.
            As he does not find the JIRA Issue Key in the e-mail subject, he should check the in-reply-to header of the e-mail to see if the first e-mail of the chain created an issue, and it seems the system is not doing that.

            *Steps to reproduce*

            # Send an e-mail to create and issue with a Cc to yourself or another e-mail.
            ## This e-mail has the example ID: 1234
            # Wait for the issue to be created.
            ## JIRA replies with an e-mail that has the example ID: ABCD
            # Now, using the CC address, just reply the email with ID: 1234 that created the issue.

            The handler is not following the In-reply-to ID.

            Expected behavior - The reply should be added as a comment to the issue.
            Actual behavior - The reply is creating a new issue. (Duplicated one)
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-30293 [ JRACLOUD-30293 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-server enterprise mail ondemand warranty New: affects-cloud affects-server enterprise mail ondemand warranty
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: enterprise mail ondemand warranty New: affects-server enterprise mail ondemand warranty

              edalgliesh Eric Dalgliesh
              pvieira Paulo Vieira
              Affected customers:
              4 This affects my team
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: