Seems to me to implement the changes could take some time and effort +
feed back the changes to Eventum developer team as a patch for general
availability. As we need to roll out Eventum before that, with a level
of email integration I am considering to use the following use case flow:
- Each project will have its dedicated email address assigned to
- Issue autocreation is turned off
This way email conversation belonging to an existing Eventum issue will
be fine until the the In-reply-to field is returned back properly. In
all other cases the emails will be loaded into Eventum and will be in
"pending" status, see "Associate Emails" link. The project manager will
check these pending emails and will either associate to corresponding
existing issues or create new issues based on them.
At least we can start using Eventum and in the meantime can work on the
Ed Sawyer wrote:
>Hi Tibor -
>We have the exact same issue with our installation of Eventum. For now,
>we have disabled the Email integration as it relates to emailing Eventum
>and getting it to track issue updates via email.
>However, we had the same thought, to embed the issue ID in the subject
>line, which should work fine with Exchange.
>I'll be curious to find out any info that relates to this also, e.g.
>which PHP programs need adjustment and such. It should be a fairly
>simple task to change where the scripts look for the issue number,
>If we get to this sooner than you do (or the maintainers do), I'll post
>whatever methods and results we came up with.
>>The "In-reply-to" field does not get back in every cases so I am
>>evaluating the option to embed the issue id into the subject field
>>for all mails sent by Eventum and then parse the subject for the
>>issue number in the case of missing "in-reply-to" field. Can you
>>point me out which php scripts would be in need of change to
>>implement this? And if possible some ideas about what would be
>>easiest way (and in line with Eventum design) to achieve the above?
>>Looking forward for any suggestions and really appreciate the help,
>>End of eventum-devel-plain Digest