Page Comparison

Summary

This section allows you configure user domains that can and cannot create/update issues. For additional information see: Use Email Allowlisting and Blocklisting within a Profile?

...

Configuration Options

Allowlist

Sender Must Have Account

...

If enabled, the sender address must be related to a Jira account holder and if not then a issue will not be created.

Allowlist Senders

...

This is a

...

CSV text-box that can contain multiple Regexps that will be used to check if the email sender matches. If any of the Regexp's match then it will mean that the email sender can create/comment using that profile.

Note: If you have multiple Regexps then you would need to place a comma between each Regexp value. e.g.

Code Block
.*@thepluginpeople.com,admin@localhost

Blocklist

Blocklist Senders

...

This is a CSV text-box that can contain multiple Regexps that will be used to check if the email sender matches. If any of the Regexp's match then it will mean that the email sender cannot create/comment on issues using that profile.

Note: If you have multiple Regexps then you would need to place a comma between each Regexp value. e.g.

Code Block
.*@localhost,spam@.*

Blocklist Recipients

A Regex configuration that will stop matching recipients/participants from being added to the issues.

This is a CSV text-box that can contain multiple Regexps that will be used to check if the email recipients matches. If any of the Regexp's match then it will mean that the email recipient will not be added to the issue.

Note: If you have multiple Regexps then you would need to place a comma between each Regexp value. e.g.

.*@localhost,external@.*

Blocklist Match Handling

...

This identifies what should happen with the email if the sender has been Blocklisted

Related Pages