User configuration
- 1.1 Reporter Name
- 1.2 Assign User Strategy
- 1.3 Assignee Name
- 1.4 Add Jira sender as watcher
- 1.5 Add Jira participants as watchers
- 1.6 Add Jira sender as Request Participants
- 1.7 Add Jira participants as Request Participants
- 1.8 Share Created Requests With Organization
- 1.9 Add To recipients to Multiuser Custom Field
- 1.10 Add Cc recipients to Multiuser Custom Field
- 1.11 Auto create Jira user
- 1.12 Auto create Jira Service Management Customer
- 2 Related Articles
The project mapping User section allows specific Jira field values (e.g. Reporter, Assignee) to have default values overridden.
For instance, the reporter field can be set, allowing the selected user account to be used as the default reporter, as opposed to the default reporter configured in your Jira project.
Reporter Name
By default, JEMHC uses the sender address or the JEMHC Application User as the reporter. This option allows you to configure the user to use as the reporter when the sender is not a Jira user. If the sender is a Jira user then that matching user will be used.
Assign User Strategy
The strategy used to set the Assignee user can select the following options:
Default Assignee (Default) - Uses the default Assignee in the Jira Project settings.
Assign to first recipient - The assignee will be the first recipient found from the incoming email (regardless of the recipient header used)
Assign to first To: recipient - The assignee will be the first recipient found from the incoming email in the ‘To’ header
Assign to first Cc: recipient - The assignee will be the first recipient found from the incoming email in the ‘Cc’ header
Assign to reporter - The assignee will be the reporter value (if applicable) based on the sender address, or the ‘reporter name’ setting above.
Assignee Name
A default Assignee can be configured to override Jira’s default Assignee in your project settings.
Add Jira sender as watcher
When the email sender matches a Jira user, enabling this setting will add the user as a ‘Watcher’ to the Jira issue.
Email addresses that match a Profile Catch Email Address will not be added to this field.
Add Jira participants as watchers
When the email participants match Jira user accounts, enabling this setting will add the participants as a ‘Watcher’ to the Jira issue.
Email addresses that match a Profile Catch Email Address will not be added to this field.
Add Jira sender as Request Participants
When the email sender matches a Jira user, enabling this setting will add the user as a ‘Request participant’ to the Jira issue.
Email addresses that match a Profile Catch Email Address will not be added to this field.
Add Jira participants as Request Participants
When the email participants match Jira user accounts, enabling this setting will add the participants as ‘Request participants’ to the Jira issue.
Share Created Requests With Organization
When enabled, requests created by a customer account part of an Organization will be shared with the organization. Disable this setting to prevent the request from being shared with the organization.
Add To recipients to Multiuser Custom Field
When a custom field has been selected, any To recipients matching Jira user accounts will be added into the selected Multi User custom field.
Add Cc recipients to Multiuser Custom Field
When a custom field has been selected, any Cc recipients matching Jira user accounts will be added into the selected Multi User custom field.
Auto create Jira user
When enabled, new Jira user accounts will be created for incoming sender addresses that do not match an existing Jira user. Disable this setting to prevent new user accounts from being created.
This setting must be disabled if you intend to configure email only user notifications.
Auto create Jira Service Management Customer
When enabled, new Jira user accounts will be created for incoming sender addresses that do not match an existing Jira user.
This setting must be disabled if you intend to configure email only user notifications.