Issue Summary

Automation rules do not set the 'sendMail' attribute in bulkOperationMetadata when sending emails, causing confusion between automation-triggered notifications and issue updates. This leads to system delays and blocking when processing bulk events.

Recommendation:
Introduce the 'sendMail' attribute to automation rules in bulkOperationMetadata, providing a consistent way to identify notifiable events, regardless of whether they are triggered by user actions or automation rules. This change will help to prevent system delays and blocking during bulk event processing.

 

This is reproducible on Data Center: (yes) / (no)

Steps to Reproduce

1. Log in to Jira Cloud.
2. Create an automation rule that sends an email notification.
3. Create or select an issue to be updated via bulk edit.
4. Use the bulk edit feature to update the selected issue(s), ensuring that the 'Send Email' checkbox is checked.
5. Observe that the 'sendMail' attribute is added to the bulkOperationMetadata for the bulk edit issue update.
6. Observe that the automation rule does not add the 'sendMail' attribute to the bulkOperationMetadata when sending an email notification.

Expected Results

• Automation rules should add the 'sendMail' attribute to the bulkOperationMetadata when sending email notifications during bulk events, similar to the bulk edit issue update behavior.

Actual Results

• Automation rules do not add the 'sendMail' attribute to the bulkOperationMetadata when sending email notifications, causing confusion between automation-triggered notifications and issue updates.

Workaround

Implement a check in the system to verify if the user who made the change matches the automation user. However, this workaround has limitations, as it cannot differentiate between automation rules with send notifications enabled or disabled.

Add a custom 'sendMail' attribute to automation rules, similar to the bulk edit issue behavior. This will allow the system to distinguish notifiable events triggered by automation during bulk events.