Issue Summary

When batching email notifications is enabled, Jira ignores the project-specific "Receive replies at" address and instead uses the global SMTP "Receive replies at" to set the Reply-To header in outgoing notification emails. If the global SMTP "Receive replies at" field is empty, the Reply-To header is absent entirely,even when a project-specific address is configured.

Steps to Reproduce

1. Set up a Jira Data Center instance with an outgoing SMTP mail server.

1. In the SMTP server configuration, set “Receive replies at” to abc@test.com.

1. Create a test user with a valid email address.

1. Enable Batching email notifications.

1. Go to Project Settings → Notifications and set the project-specific “Receive replies at” to def@test.com.

1. Create an issue and assign the test user as the reporter.

1. Trigger a notification — add a comment or change the issue status.

1. Inspect the Reply-To header of the received notification email.

• • Observed: Reply-To: abc@test.com (global SMTP value)

1. Now clear the SMTP server “Receive replies at” field (remove abc@test.com).

1. Trigger another notification and inspect the email headers.

• • Observed: Reply-To header is missing entirely.

1. When batching is disabled, the Reply-To header correctly reflects the project-specific "Receive replies at" address.

Expected Results

The Reply-To header in notification emails must always reflect the project-specific “Receive replies at” address when one is configured, regardless of whether batching is enabled or disabled.

Actual Results

• When batching is enabled, the Reply-To header uses the global SMTP “Receive replies at” address instead of the project-specific one.

• If the global SMTP “Receive replies at” field is empty, the Reply-To header is absent — even when a project-specific address is set.

Workaround

Disable batching email notifications in your Jira Data Center instance.