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.
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.
In JEMH config, we would like to map firstname.lastname@example.org with Help project, email@example.com with Support project,firstname.lastname@example.org 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?
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:
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 email@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:
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.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG