-
Bug
-
Resolution: Fixed
-
Medium
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? 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
- Create 3 projects
- Associate one mail handler to each project
- Create one Email and having 3 mail handlers in "TO" field
- 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
- is caused by
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-41831] Duplicate issues creation fails - Creating multiple issues by one Email
Hi maarten.cautreels,
Can you please open a support request for your case at https://support.atlassian.com ?
Our engineers would be able to investigate your case and if it's an issue they would re-open or raise a new issue for the problem you have.
Thanks!
Cheers,
Ignat
JIRA Bugmaster.
We are running JIRA 7.2.1 and are still experiencing this issue.
It has fix versions of both 7.1-OD-01 and 7.0.2.
Consequently, you would need to upgrade to 7.0.2 to get this fix today for JIRA Server.
If you are a JIRA Cloud customers, the fix should be available on the update scheduled for Monday 23rd Nov 2015.
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].
So what do we need to do? It shows fix version of 7.1 but that isn't released yet?
What if you duplicate the message on mail server side to different sub-folders with separate mail handlers?
edit: I see it has been tried before. I think the mails have to have unique ids for this to work as the standard mail handler checks for it...
What support can do is help you verify that the bug does indeed still reproduce in the latest JIRA 6.4.x and help you come up with a feasible workaround until this issue can be fixed in product.
We escalated to support and they reported they knew of no workaround for this bug.
Hi sorin.ispas,
The issue is on Awaiting Development status which means that is currently in the backlog to be developed and being prioritised with other bugs and suggestions. There is no ETA at the moment for it's development. By keeping an eye on this bug report, you'll get updates on when it is being developed.
Here is some information on how Atlassian approaches but fixes: Atlassian Cloud Bug Fixing Policy
Cheers,
Mauro
This but still there. I'm using the Cloud version of the software.
If Alice write to Bob and myTechSupport, and Bob respond to Alice with myTechSupport in CC the system lose the capability of changing the email thread and generate a Duplicate ticket