Identify which JSM mail handler created a request or work item
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
In some cases, Jira Service Management may be configured to use both the project default JSM mail handler and a custom email account. When both are used, you may want to identify if the message was created by one or the other.
Solution
Use the request channel smart value in Automation
You can create an automation rule using the smart value {{issue.properties."request.channel.email.source".value}}, which returns the mail handler that processed the request.
For example, an automation rule can check created tickets and make changes based on the mail handler who created them. Here's an example rule that will edit the Components field if the mail handler was a custom email domain:
Trigger: When work item created
If: compare two values:
{{issue.properties."request.channel.email.source".value}}equals yourmailhandler@yourdomain.com
Then: Edit issue fields: components
Another option is to add the value returned as the value of a "Mail handler" custom field in your work item. This also makes this information available in filters/dashboards:
Trigger: When work item created
Then: Edit work item fields: mail handler
Field value:
{{issue.properties."request.channel.email.source".value}}
In the above example, a Select list custom field was created named "Mail handler.” In this case, the email addresses of the handlers must be added as field options for the smart value to work correctly.
After creating the automation rule, send one test request through the default JSM mail handler and one through the custom email account, and confirm the rule correctly distinguishes them (e.g. sets the expected Components value or populates the custom "Mail handler" field) for both.
The smart value's limitation on System incoming mail refers to Jira's platform-level default mail handler (used when no JSM-specific email channel is configured) — if your project relies on this platform-level handler rather than a JSM custom email account, this smart value won't be able to distinguish the source.
This smart value doesn't work for System incoming mail or to return aliases. For options with aliases, please check Using custom mail handler aliases to route incoming requests.
Was this helpful?