| Info |
|---|
Fomerly Formerly known as Treat unprivileged as non-Jira. |
...
When Flexible Reporter is enabled, these conditions then one of the following will apply:
If
...
Reporter Action is set to “Jira” then the Issue will be created by “Default Reporter” with the Reporter being set
...
as the
...
Sender User.
If Reporter Action is set to “non-Jira” and the
...
Reporter Condition is set to “No application access” then it will mean that the above (point 1) will apply unless the sender user does not have any Application Access, in this case it will mean that the Issue will be created by “default reporter” and the sender being added to the configured Email Only Sender Custom Field.
If Reporter Action is set to “non-Jira” and the Reporter Condition is set to “No user Groups” then it will mean that the above (point 1) will apply unless the sender user does not have any Groups, in this case it will mean that the Issue will be created by “default reporter” and the sender being added to the configured Email Only Custom Fields.
Enable Flexible Reporter at:
...
The two available options for this configuration setting are Jira and non-Jira.
When set to Jira, it will result in the “Default Reporter” being used to create the issue, but it will set the Reporter to be the sender of an email
...
.
When set to non-Jira, then the
...
Jira behaviour will be
...
applied unless the sender
...
matches the
...
Reporter condition,
...
if they match this condition then they will be treated as a Email Only User and will have the issue created as the “Default Reporter” with the email sender being added to the Non-Jira user sender address to Text custom field which can be found at:
JEMH > Profile Configuration > Email > Sender Processing > Non-Jira user > Non-Jira user sender address to Text custom field
| Note |
|---|
|
Treat unprivileged sender (Jira user) Reporter condition
This is the condition that will be applied when the sender user must match against, Reporter action is set to “non-Jira”, this is the condition that the sender must match in order to be treated as a non-Jira user and have their email address added to the Non-Jira user sender address to Text custom field found at:
JEMH > Profile Configuration > Email > Sender Processing > Non-Jira user > Non-Jira user sender address to Text custom field
The available options are No groups and No application access. When set to No groups, the sender (Jira user)will be added :
No user Groups - this will add the sender to the Non-Jira user sender address to Text custom field if they are not a member of any Groups on your instance.
...
No application access
...
- This will add the sender
...
to the Non-Jira user sender address to Text custom field if they are not a member of any Groups
...
that
...
grant them Jira Software or Jira Core application access
...
.
...
This is only able to be configured when the Treat unprivileged sender (Jira user) Reporter action configuration setting is set to non-Jira.
| Note |
|---|
|
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|