| Setting | Description | Example |
|---|---|---|
| outgoing_email.from_address | Overrides default Jira's outgoing SMTP server from address in outgoing emails. Can be customized as per project level using this notation: outgoing_email.from_address.ABC Where ABC is your Jira project key for which you override from address | outgoing_email.from_address=support@mycompany.com outgoing_email.from_address.ABC=supportabc@mycompany.com |
| outgoing_email.from_name | Overrides default Jira's outgoing SMTP server from name in outgoing emails Can be customized as per project level using this notation: outgoing_email.from_name.ABC Where ABC is your Jira project key for which you override from address | outgoing_email.from_name=Jack Smith outgoing_email.from_name.ABC=John Dough |
| show_addon_to_pa | If set to "true" then Raley Emails Notifications will be visible to Jira users with role Project Admin. Otherwise, the add-on is only visible to Jira admins and sysadmins | show_addon_to_pa=true |
| EVENT_PROCESSING_DELAY | Delays processing of Jira/JSM events by Raley by specified number of seconds. By default, there's no delay and events are processed as soon as possible. | EVENT_PROCESSING_DELAY=15 |
| APPLY_ISSUE_FORCE_STORE | Makes a call to MutableIssue.store() function before proceeding with evaluation of notifications configurations. Sometimes this is useful to ensure that the issue is in the right state so it will match expected Raley notification configuration conditions. By default, no call to MutableIssue.store() is made | APPLY_ISSUE_FORCE_STORE=true |
