Addressee Processing

Owned by Ryan Clifton
Last updated: May 31, 2023
2 min read

Summary

This configuration is used to define where Addressees can be added (e.g. Custom Fields) and also allows you to set the Custom Fields that Non-Jira user addresses should be saved within.

 

Configuration Options

Addressee Handling

Defines how addressees should be involved within the issue. Current options are:

  • toWatcher - Adds Jira Users into the Watchers field

  • toCustomField - Adds the recipients into the configured Custom Fields

  • toJSDRequestParticipants - Adds Jira Users into the JSD Request Participants field

  • firstCCIsAssignee - Adds the first Jira User from the Cc header as the Assignee of this issue. Note: Only applies during issue creation.

Request Participant Filter

Defines who can be added as a Request Participant on the issue. Current options are:

  • requireCustomerRole - This will add all users that has the Customer Role. This includes users with multiple roles. e.g. Customer role and Team role

  • requireOnlyCustomerRole - This will add Users that ONLY has the Customer Role. Users with multiple roles will not be added to the issue. e.g. Customer role and Team role.

  • requireNoUserJira -

  • none - Will all found Users/Email address to the relevant fields on the issue. (Defined in Addressee Handling)

Assign non jira-user Email to Text CustomField

Defines the Text Custom Field that non jira-users recipients will be added to.

Jira account holders to MultiUser Custom Field

Defines the MultiUser Custom Field that recipients with a Jira account will be added to.

CC non-Jira Emails Custom Field

Defines the Custom Field that Cc’d non-jira emails will be added to.

Distribution List Extraction

Distribution List extract LDAP Config

The LDAP configuration that can provide access to the definition of the distribution lists.