JEMH: Field based on catch mail address?

Hello,


I have Support Emails from two email addresses running into one JIRA project using JEMH.
To do this, I'm forwarding the emails from email2@domain.com to email1@domain.com, and entered both into the "Catch Email Address" field in the JEMH Project Settings.
However I would like to differentiate the Issues based on which address the email was sent to (preferably by a field).
I currently use the following settings:

  • Sender processing: jira-user > Assign jira-users Email to Text CustomField: External Mail
  •  processing: non jira-user > Assign non jira-users Email to Text CustomField: External Mail

This creates a for each incoming mail an "External Mail" field in the issue with the senders Email address.
If I want to have a similar field for the addressee, there are the "Addressee Processing" options. According to https://thepluginpeople.atlassian.net/wiki/display/JEMH/How+do+email+address+get+mapped+to+custom+fields I have entered the following values:

  • Addressee Handling: toCustomField
  • JIRA account holders to MultiUser Custom Field: I'm not entirely sure why this is a user picker and not a field picker.
  • Assign non jira-user Email to Text CustomField: Addressee


I have correctly set the screens for the Addressee CustomField (same as for External Mail), yet it doesn't appear in the issues.
PS: email1@domain.com is also a JIRA user, email2@domain.com is not.
===========

  • What do I have to do to get the Addressee field displayed in the issues?
  • Would this even work to differentiate between email1 and email2 since they both come from the same mailbox?
  • If you can provide a solution, could this field be used to automatically assign the incoming issues to certain users?

Thanks in advance
Sebastian

 

2 answers

1 accepted

1 votes
Andy Brook Community Champion Feb 09, 2017

> What do I have to do to get the Addressee field displayed in the issues?

Simple enough, use a Project Mapping for the target project, with a Domain rule for the inbound address in each case, then you could set the address statically for a given TEXT single line custom field.  This would then expose the TO: address in a custom field.  Then, you would be able to use that in the Event Listener.

> Would this even work to differentiate between email1 and email2 since they both come from the same mailbox?

So long as the original recipient address is listed somewhere in the email this should be possible.  Most mail servers retain the original TO: address, others put it in an additional EmailHeader (this is where the JEMH CatchEmailHeader field comes in, you nominate where to look)

> If you can provide a solution, could this field be used to automatically assign the incoming issues to certain users?

Use each domain Rule to nominate an Assignable user as the assignee in each project.

Note: the Default Project Mapping has no rules, its intentional, use a different project for the Default Project Mapping that your expected project, its there to handle addressees that are IN the catchemail list, but NOT mapped.

Hi Andy

Thanks so much for the help! Project Mappings were the key.

Here is my solution, for anyone interested:

  • Create a Project Mapping
    • Mapped Project: set Project
  • Create 2 Domain Mappings within the Project Mapping
    • Email domain mapping: email1/2@domain.com

    • Match against the addressee: [x]

    • User Custom Field: Addressee == email1/2

    • Assignee: set default Assignee

(Only question I have left is: What does the Event Listener have to do with this? I didn't change anything there...)

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

655 views 4 15
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot