Suppressing the email when Jira Automation adds a comment

Description and use

In Jira Cloud, automation that adds a comment does not suppress email notifications even when a sendNotifications flag is added to the exported rule JSON. The fix is to use the REST API with notifyUsers=false when updating the issue, which successfully suppresses the emails.

Problem

Jira Automation’s Comment action does not suppress email notifications even when a sendNotifications flag is added to the exported rule JSON.

Outcome

Using the REST API with notifyUsers=false successfully suppresses email notifications for comments added by automation, whereas the Comment action’s sendNotifications flag is ignored.

Workflow

• 1. Open the rule builder and check if the Edit work item action still offers a notification checkbox. If it does, restructure the rule to use Edit instead of Comment. 2. If the checkbox is absent or a comment is required, use the Jira REST API to add the comment via an issue edit request with notifyUsers=false. 3. Construct a PUT request to /rest/api/3/issue/{issueKey}?notifyUsers=false with a JSON body that includes the comment in the update.comment.add field. 4. Execute the request with an account that has Administer Jira or Administer Projects permission. 5. Verify the comment appears and no email is sent to watchers.

Evidence

sendNotifications is not a parameter of the automation Comment action, so nothing reads it.

Source

The Jira comment REST endpoint ignores unknown keys silently. I posted sendNotifications, notifyUsers and totallyMadeUpKey12345 to it and all three returned 201.

Source

notifyUsers is real — on Edit issue, on Update comment and on the worklog endpoints. The one place it does not exist is ADD comment, which is exactly the operation automation performs.

Source

So "just call the API instead of using automation" is only a fix if you call that endpoint. Posting to /issue/{key}/comment gets you nowhere no matter what you attach to it.

Source