A single JEMH profile supporting multiple distinct projects?

[Simon Gao]

Hi,

Will JEMH for Jira 6.x support one single profile working with multiple distinct projects? I.e. each project has different fitering criteria. Some needs strip quoted contents while others do not for example.

Simon

[Andy Brook [Plugin People]]

Hi Simon, JEMH has an overall configuration 'the Profile', it has Project Mappings, each of which allows per-project overrides of many fields common to issue creation, each Project Mapping can have many Rules, each of which again can have overrides of the containing Project Mapping for per-rule tailoring. Can you expand on what you mean by 'filtering criteria'? The Rules allow routing based on: - domain (addressee and sender) - group (JIRA user group membership) - subject keywor d There are some params that have not yet made it into ProjectMappings or Rules. There isn't a specific reason for not including more fields, just that nobody has asked! There are many fields that could be added, in the content related bucket, yes, de-quoting settings are one, in addition, the latest HTML to wiki conversions and whitespace injection could all be use to tailor a result, just waiting on real world need before spending the time. Please log a feature request if this is a blocking feature-gap. - https://thepluginpeople.atlassian.net/browse/JEMH

[Simon Gao]

Hi Andy,

We don't want to use meta/key word in subject line or email contents for JEMH to use when sorting incoming emails into different projects.

All we want is JEMH acts on a specific destination email address and based on that email address, JEMH would know which project the email should be added to.

For example, we have three incoming email addresses: help@example.com, support@example.com, sales@example.com. There are three projects, Help, Support, Sales.

In JEMH config, we would like to map help@example.com with Help project, support@example.com with Support project,sales@example.com with Sales project. Each of the mappings gets a different rules applied to it.

In summary, the key/meta word in subject line/mail content is hard to use.

Is this possible?

Simon

[Andy Brook [Plugin People]]

Hi Simon, yes, that is the Domain Mapping Rule, from the looks of the examples, you want 'addressee' matching.

To do this you would create Project Mappings as follows:

Help

• Domain Mapping Rule: help@example.com

Sales

• Domain Mapping Rule: sales@example.com

Support

• Domain Mapping Rule: support@example.com

As I described, each Project Mapping can define 'per-project' defaults for many fields, which can be overridden on a per-rule basis also.

Keyword matching can work if you are selective, and want to futher 'route' traffic to components and their owners, for example, within support@example.com, if someone says 'password' or 'locked out' etc, you may want to route that to a 'User Management' component, whereas anything saying 'network' might be routed to a 'Network Management' etc.

There is a How To on Project Mappings:

- https://thepluginpeople.atlassian.net/wiki/display/JEMH/Use+Project+Mappings

[David Turner]

Hi Andy,

Just FYI.

Reading through these guides, I've just been working through to set up something similar with several inbound email addresses (for separate projects) arriving in one capturing mailbox at our site. This is critical through the dev and user transition phase to ensure the old manual Email-based processes can be fully replaced (with no information lost) by the new Jira solution.

Domain mappings for 'addressee' will solve this nicely. And for more complicated configurations, I see that different profiles could be set up with Non-catch/Ignore option to leave messages for a subsequent email processor; great.

Now it is probably worth adding a link in your documentation that outbound Notifications from JEMH can also have a configured sender email address per project, so that if the recipient replies to a notification email it will hit the correct inbound mail address for that project. This is achieved through the Event Listener - Project specific configurations.

And on that same screen, add each address (regexp) comma-separated to the disabled domains field, so outbound notifications do not cause any loopbacks.

[Andy Brook [Plugin People]]

Hi David,

Glad to hear JEMH has all the cases covered! Yes, I've added this to the How To Use Project Mappings guide as an info bubble.

thanks!