Flexible Reporter

Owned by Kyle McEwan
Last updated: May 16, 2024 by Ryan Clifton
3 min read

Formerly 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, then one of the following will apply:

  1. 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.

  2. 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.

  3. 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:

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, 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

  • 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 will be applied when the 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:

  1. 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.

  2. 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.