...
In order for a project mapping to be selected during email processing, it must have a valid Mapping Rule attached to it. A rule defines a condition that an email (or data derived from it) must pass, and is considered valid if its conditions are passed.
| Gliffy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
When you should use Project Mappings
...
This rule allows custom logic to be used to determine if a match is made. /wiki/spaces/JEMH/pages/223739905 More information on using the script rule type.
Domain Rule
This rule checks the sender or recipient addresses of an email for a match against the user-defined value. This value is regular expression capable, meaning that a pattern can be defined instead to allow matches to many different addresses.
...
After saving and clicking on the Domain Rules at the top
...
you You can view the created Domain Rule:
...
Addressee Rules function as Catchemails
| Status | ||||
|---|---|---|---|---|
|
To save duplicate data entry for Profile > Email Catchemail Addresses, Addressee domain rules are now interpreted as a ‘mailbox address’ and are now effectively the same as Profile > Email Catchemail Addresses. Profile advisories will be issued to highlight redundant Profile > Email Catchemail Addresses entries.
Group Rule
Group mapping rules allow routing of mail based on JIRA user group membership. Therefore the user sending the email needs to be associated with a JIRA account for this rule to work.
...
Each rules current priority can be viewed at either the rule level or mapping level:
Viewed at project mapping level | Viewed at project configuration level |
|---|---|
 |  |
Processing-time feedback
When running Test Cases, and shown in Auditing, some more information is available to help users understand what rule matched and was applied, here is an example relating the the above, the domain of the sender is .*@localhost
...
Adding a few of each kinds of Rule, the effects of the sorting are visible. There are also one-click Up/Down action links that work by switching the position of the two entries (currently the up/down actions page refresh - in future this will be improved with AJAX):
Domain Rules | Group Rules | Keyword Rules |
|---|---|---|
 |  |  |
Default project mapping
The Default project mapping applies when no other mapping is found to match. It allows issue attributes to be inherited when they are not defined elsewhere. Unlike a normal project mapping, default mappings do not have any rules associated with it.
...
To set a mapping as the default, enable the Default Mapping check-box setting and submit the form.
...
Once Submit has been clicked, re-edit the default mapping. You will see that the words "Default" will appear next to the issue attributes fields to signify that that any values that the user enters here will be used as the default:
...