Bug #19943 Email retrieved into the wrong project
Submitted: 19 May 2006 13:27 Modified: 22 May 2006 6:48
Reporter: Rick Mulder Email Updates:
Status: Closed Impact on me:
None 
Category:Eventum Severity:S3 (Non-critical)
Version:1.7.1 OS:Linux (Debian Linux)
Assigned to: Bryan Alsdorf CPU Architecture:Any

[19 May 2006 13:27] Rick Mulder
Description:
The problem occurred when someone (project A) wanted to assign an issue to another project (Project B) and put the emailadres of project B in the notification list and then replied to this issue.

The email was received in the mailbox of project B but had the issue #nr of project A. Then the email was being imported into eventum and it was not assigned to project B (apparently because the issue_id already existed). 

How to repeat:
1. Create two projects (A & B) with each its own mailbox. Create issue #1 in Project A. 

2. Then send a mail to project B with in the subject '[#1] This is an issue for project B!'.

3. Retrieve the mailbox for project B and check your issue list in project B. Without any warning this mail is appended to issue #1 in project A.

Suggested fix:
Moving issues from one project to the other would be nice. But at least a warning that the issue_id is already in use, might be usefull.
[19 May 2006 16:22] Bryan Alsdorf
Rick,

Do you have subject based routing enabled? If so, there really isn't anything to do to fix this. If it is not enabled, then yes it is a bug and I will look into it. 

We are also looking into moving issues between projects in the future.

Best Regards,
/bryan
[20 May 2006 18:14] Rick Mulder
Hi Bryan,

Subject based routing is enabled! So this isn't a bug then?

Gr,
Rick
[22 May 2006 6:48] Bryan Alsdorf
Rick,

I would not call it a bug, just an unfortunate shortcoming. If you can setup email routing (issue-xxx@example.com), you will find it is much more robust.

Best Regards,
/bryan