Flexible Reporter

Fomerly known as Treat unprivileged as non-Jira.

Flexible Reporter

As an administrator, you want enabled JIRA account holders to be involved in Projects and Issues where they do not have the required Permissions.

When Flexible Reporter is enabled, these conditions will apply:

  • If the (Jira user) Sender has no Issue permissions or right to use, they will be treated as “email users” with the Reporter being set to the “default Reporter”.

  • If the (Jira user) Sender has Issue permissions but not right to use, then the default reporter will create the issue, and set the reporter as that user.

Enable Flexible Reporter at:

JEMH > Profile Configuration > Security > Flexible Reporter

This feature Makes use of JEMH non-JIRA account holder support, where email addresses are stored in a custom field.

  • Enabling this support would allow anyone to mail into these projects, email domain restrictions can be enforced through Whitelist/Blacklist rules – see Use Email Whitelisting and Blacklisting.

  • Any users listed as non-JIRA will be processed via Event Listener Project Mappings as non-JIRA, individual user preferences will be currently ignored.

Treat unprivileged sender (Jira user) Reporter action

The two available options for this configuration setting are Jira and non-Jira. When set to Jira, the sender of an email will be treated as a Jira user, whereas, when set to non-Jira, the sender will be treated as non-Jira and if set and the sender user matches the set Treat unprivileged sender (Jira user) Reporter condition, their email will be 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

  • This is only available and shown in the UI when Flexible Reporter is enabled.

Treat unprivileged sender (Jira user) Reporter condition

This is the condition that the sender user must match against, to be treated as non-Jira and their email 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 to the Non-Jira user sender address to Text custom field if they are not a member of any Groups on your instance.

When set to No application access, the sender (Jira user) will be added to the Non-Jira user sender address to Text custom field if they are not a member of any Groups on your instance that have Jira Software or Jira Core application access.

  • This is only available and shown in the UI when Flexible Reporter is enabled.

  • This is only able to be configured when the Treat unprivileged sender (Jira user) Reporter action configuration setting is set to non-Jira.

The Treat unprivileged sender (Jira user) Reporter action and Treat unprivileged sender (Jira user) Reporter condition features only applies for Software and Core applications, not JSM
If you would like to use these Treat unprivileged sender (Jira user) Reporter action and Treat unprivileged sender (Jira user) Reporter condition features, then another Profile will have to be used for JSM Projects.