iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
In Jira Cloud, sendNotifications: false does not reliably stop email from the native Automation Add comment action. The available documentation does not identify it as a supported notification control. If you need to suppress notifications, Atlassian’s documented workaround is to add the comment through an issue update request with notifyUsers=false—not through the separate Add comment API operation. Test the result on your own site before using it in a production rule.
Why does sendNotifications: false do nothing?
The native Jira Cloud Automation Add comment action and the Jira REST API are separate mechanisms. Atlassian’s issue smart-value documentation describes comment-related data available to rules; it does not establish sendNotifications as a supported switch for controlling mail from the native action. An Atlassian Community discussion also reports that the value is not a parameter of the action and is ignored. Treat that discussion as corroboration of the behavior, not as a formal product specification.
So an exported rule that contains sendNotifications set to false should not be taken as proof that the action will suppress email. The available sources do not document that field as a supported control.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Can the Add comment REST endpoint use notifyUsers=false?
Not as a documented parameter of Jira Cloud REST API v3’s Add comment operation. That operation documents expand, not notifyUsers, so adding notifyUsers=false to the Add comment request is not the documented solution.
#1 Best Overall
What workaround does Atlassian describe?
Atlassian’s JRACLOUD-97682 feature request identifies the limitation and describes a workaround: use the Jira Cloud REST API’s Edit issue operation to submit the comment as part of an issue update while setting notifyUsers=false. This is an API-based alternative to the native Automation action; it is not a setting on the native Add comment action or the Add comment endpoint.
In Automation, the rule can use Send web request to call the relevant issue update route. The account used for the request needs appropriate authentication, API scopes, and issue permissions. The request body must also match the target deployment’s API requirements. The feature request establishes that this workaround exists, but does not validate a particular customer’s credentials, scopes, payload, or site configuration; verify those details against the Jira Cloud REST API v3 overview and your own setup.
Choose between the native action and an API request
| Approach | What it does | Notification control | What to check |
|---|---|---|---|
| Automation Add comment | Adds a comment using the built-in rule action. | sendNotifications: false is not established as a supported control; do not rely on it to silence email. |
Confirm actual mail behavior in the target Jira site. |
| REST API Add comment | Adds a comment through the dedicated comment operation. | The documented Cloud v3 operation does not list notifyUsers. |
Do not assume that adding notifyUsers=false to this operation suppresses notifications. |
| REST API Edit issue with a comment update | Submits a comment as part of an issue update. | Atlassian’s feature request describes this route with notifyUsers=false. |
Validate request construction, permissions, scopes, and resulting notifications. |
How to validate the change safely
- Confirm the deployment. This guidance covers Jira Cloud and its REST API v3. Check the documentation for your specific version before applying it to Data Center or older Server installations.
- Test outside production. Create or choose a test issue with representative notification settings and recipients.
- Check the API request. Ensure the request uses the issue update operation, carries the comment in the issue update payload, and includes
notifyUsers=falseas described by Atlassian’s workaround. - Verify authorization. Confirm that the account making the web request has the necessary authentication, scopes, and permissions for that issue.
- Observe actual outcomes. Check whether the comment was created and whether the intended recipients received email. Jira notification schemes, recipients, comment visibility, and site configuration can affect what users receive, so do not assume the setting suppresses every notification in every configuration.
What comment smart values can—and cannot—do
Jira’s issue smart values include details about a triggering comment, such as its body, author, creation time, visibility information, and internal status. Those values can help a rule identify which comment or visibility case it is handling, but they are data for rule logic—not notification suppression controls.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Scope: Jira Cloud only
The parameter conclusions here are based on Jira Cloud Automation documentation and Jira Cloud REST API v3 references. They should not be applied automatically to Data Center or older Server installations; consult the documentation for the version you run. Atlassian’s REST API v3 overview provides the Cloud API context.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
