-
Bug
-
Resolution: Fixed
-
Medium
-
5.2-m06, 5.2
-
JIRA 5.2-m06-4 (OnDemand)
-
5.02
-
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
- 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)
- is caused by
-
JRASERVER-9979 NotificationInstance's should have a creation date, and a service to clean them up
- Closed
- is duplicated by
-
JRASERVER-30484 Add comments (from email) to the issues without replying to email notification
- Closed
- relates to
-
JRACLOUD-30293 Duplicating issue when replying to e-mail
- Closed
-
JRASERVER-37319 Email threading can break due to milliseconds being dropped in the In-Reply-To value
- Closed
-
JRADEV-17100 Loading...