Scenario
You want to identify a project through email and a JEMH Profile.
Project > Fallback project
A profile can define exactly one fallback project (Project > Fallback Project). This is used if the absence of any other project selector.
Project > Project Auto Assign
This feature uses the addressee part of the email to indicate the project, eg abc@yourco.net would try to locate a project with key ABC (case insensitive). This feature is the best way to support arbitrary numbers of projects but requires the mailbox to collate all addressees within it (one mailbox, all addresses for the domain). This can be achieved using off the shelf open source technologies such as Postfix and Dovecot with Virtual Mailboxes.
Project > Project Auto Assign from Subject
This feature allows users to indicate the project KEY through a regexp that MUST have a single capture group, such as:
.*(#[0-9]{4}).*
The first capture group is the content of the first logical set of ( ). This allows an externally (fixed) email subject to drive the selection of an appropriate project key.
NOTE: Atlassian are moving toward a strict alphabetical project key format, historically this could be configured.
Project > Project Auto Assign from Sub-addresses
@since 1.3
This is a variation on Project Auto Assign, it allows sub-addresses to be provided that are used as the assignee, for example, the following will cause the 'assignee' to be defined as user. This operation is outside of JEMH Directives and so will work with the Basic Field Processor.
user+support@myco.net
Project Mappings
JEMH Project Mappings allow a single profile to route email to target projects, mappings can be created from:
- the incoming addressee
- the remote sender (from
- the groups held by the remote JIRA user
There is no specific limit on project mappings other than usability. Future work will make management of large numbers of projects more user friendly.
See Use Project Mappings more details on project mapping and the additional per-mapping customizations that can be made.
Field Processors
JEMH supports many Field Processors, some of these are very specific regarding the content of the email that they process, and as such, may define a specific project to use (e.g. Nagios Field Processor/ Regexp Field Processor)
Directives
Most of the JEMH Field Processors allow the use of Directives (if enabled). These directives allow remote users to drive JIRA into using a specific project. Directives can be supplied in a variety of ways, from Subject, lead in part of the Body, even X-JEMH mail headers for 'invisible' manipulation.
At Prefix
@project=ABC
Colon suffix
project: ABC
Subject
Subject: hello there #project=ABC
X-JEMH mail header
X-JEMH-project: ABC