Add TO and CC email adresses to custom field when sending out mails with JETI

[David Ringhofer]

I want to use JETI with JEMH and thus wan't to store the info of non-jira users as a custom field. This works perfectly well when the non-jira user sends in a mail to open an issue. I have to set the custom field also when I send out a mail to a non-jira user with JETI for the repsonse to be processed with JEMH. I have tried and tried but to no avail - pointers?

[Tibor Hegyi _META-INF_]

Hi David,

This is not possible with JETI at the moment. You can only do it the other way around.

You save the non-jira recipients in the custom field by editing the issue, then you select the custom field as a recipient when you email the issue. The result is the same.

I have created a feature request issue for your case to track: https://metainf.atlassian.net/browse/JETI-95

Tibor

[Tibor Hegyi _META-INF_]

Hi David,

Let me sum up your case just to see I understand you correctly.

You import emails to create issues and comments using JEMH, right?

You store "info of non-jira users" (I suppose email address?) from incoming emails in custom fields.

JETI's mail handler stores sender and recipient email addresses in custom fields even when email is imported as a comment to an existing issue.

JETI can set To and Cc from custom fields. If you have the custom fields populated with email addresses from the initial email, you can refer to these fields as To or Cc when you send out emails using JETI.

Please use the To and Cc dropdown elements, scroll down to the section "Custom fields" and select your fields.

JETI supports text (limited or unlimited), (multi)userpicker, (multi)group picker custom fields as recipients.

What is the field type of your custom fields where you store non-jira user info?

Please let me know if I misunderstand the problem so that I can further help you.

Tibor

[David Ringhofer]

Hi Tibor!

Your description is quite right, but additionally I would like to have the following:

1) Issue is created in JIRA by a jira-user thus not having the custom field (let's call it "email") filled
2) A user uses JETI to send a mail to a non-jira user (sag "test@test.com")
3) test@test.com should be stored in the "email" custom field by JETI after sending out the mail
4) test@test.com replies to the issue via mail an JEMH se security recognises the non-jira users email adress to be valid because it's sotred in the "email" field