The Email issue post-function sends through Jira, so mail comes from your Jira site. In Who gets it:
- The reporter, The assignee, The watchers, The voters.
- Specific people, user fields, Groups and project roles.
- People worked out by a template (optional): account ids separated by commas. Groups worked out by a template (optional): group names separated by commas.
- Plain email addresses (optional): one address per line, for people with no Jira account.
Plain email addresses
- Plain addresses are for sites with Jira Service Management.
- When an address matches a person Jira can show, the email goes to that person.
- Otherwise the address is added to the site as a service project customer the first time it is used, and the email goes to that customer.
- Addresses typed into a rule, shared action or scheduled action are kept as part of that item until you delete it. Run history never stores addresses, and the app’s logs never hold them.
People who hide their address
People who hide their email address from apps cannot be matched by address and are skipped. The others on the list still get the email, and the run in run history says the address belongs to an account that hides it. To reach such a person, pick them as a user instead.
Good to know
- Each rule sends at most once for a given move and work item, even if the run is retried.
- If the list of recipients cannot be worked out, for example because role members cannot be read, nothing is sent for that work item rather than mailing part of the list.
- Email issue is for company-managed projects only.
Related pages
Need help with Simple Workflow Automation? Contact us