...
| Table of Contents | ||||
|---|---|---|---|---|
|
Email only user definition
JEMHC defines an ‘Email only user’ as:
...
| Panel | ||
|---|---|---|
| ||
JEMHC will create required custom fields for the following configuration. However, if you decide to use your own custom fields, ensure that:
|
Sender address headers
This setting defines the headers that JEMHC will check for a sender address value. (Select Inherit to inherit value using inbound email).
Email Sender Address Field
The Email sender address field allows a custom field to be defined that will store the inbound email only user addresses. By default, JEMHC will create an ‘Email Sender Address’ custom field that will work by default.
If you wish to configure your own Custom Fields, please refer to Atlassian documentation for custom field creation.
Email Sender Name Field
The Email sender name field allows a custom field to be defined that will store the inbound email only user name part(s). By default, JEMHC will create an ‘Email Sender Name’ custom field that will work by default.
If you wish to configure your own Custom Fields, please refer to Atlassian documentation for custom field creation.
Email Participants Field
The Email participants field allows a custom field to be defined that will store the inbound email participants. By default, JEMHC will create an ‘Email Participants’ custom field that will work by default.
If you wish to configure your own Custom Fields, please refer to Atlassian documentation for custom field creation.
Non-Jira security
When enabled, this setting prevents email only users that send an email matching an existing issue when the sender address is not present in an email only custom field. This is mostly enabled to prevent unwanted recipients gaining access to Jira Issues by sending an email in that relates to an existing Jira Issue.
Disabling this setting will allow anyone to send an incoming email and add themselves as recipients to the Jira Issue.
Allow Uninvolved Senders via Threading
Requires ‘Non-Jira security’ to be enabled. This setting further configures how JEMHC restricts ‘anonymous’ access for email only users.
When enabled, email only users that do not currently have access to an issue can participate in issues if the email threading matches an existing Issue.
Clear Option
This option allows you to clear the selected value from the field. This allows Email Only User configuration to be disabled for specific Rules/Project Mapping.
...
Inherit Option
This option allows you to inherit the value from either the default Project Mapping or the current Project Mapping if used within a Rule.
...
Related Articles
| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|