Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Fixed
Fix Version/s: 7.2.0, Available in Jira Cloud
Component/s: REST API
Labels:

Feedback Policy:

We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

Atlassian Update - 23 September 2016

Hi everyone,

Suppressing email notifications is now possible when editing issues. We have added a new notifyUsers query parameter to the issue resource. You can set this query parameter value to false when making a PUT request to suppress email notifications for your change. You can view the documentation here.

This will only affect email notifications – changes will still be logged, added to the issue change history, events will still be sent to listeners, webhooks will still fire.

This is currently available in JIRA Cloud and was released in JIRA Server 7.2.

Regards,
Dave Meyer
JIRA Product Management

REST api is supposed to replace XML/RPC and SOAP APIs which are already deprecated (and contains blocker bugs).

I am filing this as a bug because it is clearly a regression from using SOAP where you can skip sending notifications.

This bug makes maintenance via REST almost impossible due to the amount of emails it will send to the users.

Support suggested disabling email notifications while the scripts are running but that's not possible for two reasons: these are live systems used 24x7 and 2nd, these could be triggered at different times or scheduled to run periodially, it's not possible to disable email notifications for the entire instance just to prevent these from happening.

One possible solution to this problem is to have a special group, like jira-bots (or jira-automation, jira-silent) for which jira will skip sending email notifications if the changes were made by a user part of this group.

Attachments

Issue Links

has a derivative of

JRASERVER-70669 REST API issue create endpoint should have the ability to suppress notifications

Gathering Interest

is duplicated by

JRASERVER-41315 REST API is the ability to make changes to a ticket without triggering email notifications

Closed

is related to

JRASERVER-1369 Reduce JIRA email chatiness

Closed

JRASERVER-63577 Add the ability to add/update worklogs via REST without sending notifications

Gathering Interest

JRASERVER-67061 Add the ability to transition issues via REST without notifying users

Gathering Interest

JRASERVER-67363 Add the ability to create issues via REST without sending notifications

Gathering Interest

JRASERVER-67364 Add the ability to delete issues via REST without sending notifications

Gathering Interest

JRASERVER-73206 Add option to prevent email notifications from updates of specific users

Gathering Interest

JRASERVER-73225 Add the ability to add comments to issues via REST without sending notifications

Gathering Interest

ACJIRA-682 Loading...

relates to

JRACLOUD-34423 Add the ability to update issues via REST without sending notifications

Closed

JRASERVER-61808 Add notifyUsers flag to issue update webhook data

Closed

was cloned as

JRASERVER-61537 Add the ability to attach/delete issue attachment via REST without sending notifications

Gathering Interest

ACJIRA-391 Loading...

JSEV-624 Loading...

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...

(5 is related to, 2 relates to, 3 was cloned as, 4 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Sorin Sbarnea (Citrix)

Votes:: 135 Vote for this issue

Watchers:: 110 Start watching this issue

Dates

Created:: 21/Aug/2013 11:06 AM

Updated:: 30/Oct/2023 12:44 PM

Resolved:: 03/Jun/2016 5:41 AM