Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsIn Jira Cloud, sendNotifications: false is not a supported switch for silencing email from Automation’s built-in Add comment action. For a different approach, Atlassian’s documented workaround is to add the comment through an issue update REST request with notifyUsers=false—not to add that parameter to the comment endpoint. Validate the API call and resulting notifications on your Jira site before relying on it.
Why does sendNotifications: false do nothing?
The built-in Automation Add comment action creates the comment natively. Available evidence indicates that sendNotifications is not a supported notification parameter for that action, so including it in an exported rule or request does not reliably prevent the resulting email. An Atlassian Community report describes the same behavior; it is useful corroboration, but not a product specification.
As an Amazon Associate I earn from qualifying purchases.
Atlassian’s issue smart values documentation describes data about comments, such as the body, author, creation time, visibility, and internal status. Those values can help a rule determine which comment it is handling; they do not provide a notification-suppression control.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Can the Add comment REST endpoint use notifyUsers=false?
Not according to the documented Jira Cloud REST API v3 parameters. The Issue comments API does not list notifyUsers for its Add comment operation. Adding ?notifyUsers=false to that endpoint is therefore not a documented solution.
#1 Best Overall
What workaround does Atlassian describe?
Atlassian’s feature request JRACLOUD-97682 identifies the lack of a notifyUsers=false option on the comments API and describes a workaround: submit the comment as part of an issue update using the Edit issue REST operation with notifyUsers=false.
In Automation, this means using Send web request to call the issue-update route rather than relying on the native Add comment action. Construct a valid request for your Jira Cloud site and deployment, and make sure the account used by the request has the necessary authentication, scopes, and issue permissions. The feature request describes the approach; it does not verify a particular site’s credentials, payload, or notification behavior.
How to choose and validate an approach
| Approach | What it can establish | What to check |
|---|---|---|
| Automation’s native Add comment action | Creates a comment through the built-in action; sendNotifications: false is not an established suppression control. |
Do not rely on that value to silence email. |
| Send web request with an issue update request | Uses Atlassian’s stated workaround: carry the comment in an issue update with notifyUsers=false. |
Authentication, scopes, permissions, request validity, and actual email behavior on the target site. |
- Decide whether the rule can use the native action or needs the REST API workaround.
- If calling the API, verify the request route and body against the current Jira Cloud REST API v3 documentation and configure the calling account with the required access.
- Test on the target site and confirm both that the comment is created with the intended visibility and that the recipients receive the expected notifications.
Do not assume the workaround suppresses every type of notification in every configuration. Notification schemes, recipients, comment visibility, and site-specific settings may affect what users receive.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Which Jira installations does this apply to?
This guidance concerns Jira Cloud Automation and Jira Cloud REST API v3. It does not establish equivalent behavior for Jira Data Center or older Server installations; check the documentation for the specific version and deployment before applying the API advice.
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.
