Suppressing the email when Jira Automation adds a comment (and why sendNotifications does nothing)
Suppressing the email when Jira Automation adds a comment (and why sendNotifications does nothing) Key takeaways sendNotifications is not a parameter of the automation Comment action, so nothing reads it. Your export proves the key is stored; your inbox proves it is not used. The Jira comment REST endpoint ignores unknown keys silently. I posted sendNotifications, notifyUsers and…
Key takeaways:
- The sendNotifications parameter is not a part of the Jira Automation Comment action, so it has no effect.
- The exportable key for sendNotifications is stored in the automation rule, but it is not actually used.
- The Jira comment REST endpoint ignores any unknown parameters silently.
- The notifyUsers parameter does exist for Edit issue, Update comment, and worklog endpoints, but not for Add comment.
- Sending a value for a non-existent parameter does not indicate whether your account can use it; that depends on separate permission gates.
- The email suppression issue was verified on a live Jira Cloud site, but no API reports whether it worked or not.
- An Atlassian Community member reported the issue correctly, but it still did not work even after following all the steps.
- The flag does nothing because it is not a parameter of the comment action, and the automation engine does not look at it.
- The issue was first reported in AUTO-602 on 2 August 2026, and it remains unresolved six years later with over 1,000 votes.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
