Introduction

Project association is the matching of incoming emails to project in JIRA. When there is an incoming email and NO issue has been associated to the message, a new issue will be created in the associated project.  There are a several mechanisms through which project association can be achieved, each with varying levels of strength.  These will now be discussed, in the order that JEMHC uses to look for an association.

Project Key Directive

With a field processor enabled, a directive can be used to drive issue creation to a specific project. 

For example, the At(@) Prefix field processor allows the following directive to direct the email to a project (in this example ABC):

By Email Address

The recipient address that matches one of the profile's catch email address is tested for a project key. This association strategy can be enabled in the Profile→ Project Mapping → Project configuration page.

There are two ways of providing the project key in email addresses (in these examples, issues are created in project ABC):

Local Part

 One of the profile's catch email addresses must match ABC@mycompany.com

Sub-domain

 One of the profile's catch email addresses must match support@mycompany.com (sub-domain excluded from matching)

Project Mapping

The most common way to create issue in a project is by selecting the project in the Profile's Project Mapping. If the message applies to one of the Project Mapping's rule, the issue will be create in the Project Mapping's selected project falling back to Default Project Mapping's project.

Related articles