Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-34423

Add the ability to update issues via REST without sending notifications

    • 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.

      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.

          Form Name

            [JRASERVER-34423] Add the ability to update issues via REST without sending notifications

            Please fix it, feel helpless.

            Teams are complaining a lot because of the bombardment of emails.

            Nitun Pachauri added a comment - Please fix it, feel helpless. Teams are complaining a lot because of the bombardment of emails.

            This is not working for worklogs. If you would like this to be solved, please vote for https://jira.atlassian.com/browse/JRASERVER-63577

             

            Jean-Luc Lejoly added a comment - This is not working for worklogs. If you would like this to be solved, please vote for https://jira.atlassian.com/browse/JRASERVER-63577  

            chaorace added a comment -

            I'm having the same issue that Nick is reporting.

            Sending a request with notifyUsers=false under my user with Jira Admin will correctly suppress the notification, but sending the exact same request with our integration user that only has Project Admin sends notifications even when notifyUsers is provided and false. I've confirmed with the permission helper that the integration user does, in fact, have the project admin permission for the issue we are modifying in the request.

            chaorace added a comment - I'm having the same issue that Nick is reporting. Sending a request with notifyUsers=false under my user with Jira Admin will correctly suppress the notification, but sending the exact same request with our integration user that only has Project Admin sends notifications even when notifyUsers is provided and false. I've confirmed with the permission helper that the integration user does, in fact, have the project admin permission for the issue we are modifying in the request.

            david.faure, with ProjectAdmin a notification comes too.

            Nick Rozhdestvensky added a comment - david.faure , with ProjectAdmin a notification comes too.

            @oleg.pronchenko https://stackoverflow.com/questions/13017931/disabling-jira-notification-emails-for-rest-api-updates/13025457?noredirect=1#comment89310388_13025457 says you need ProjectAdmin or Admin rights for notifyUsers=false to work. For some reason.

            David Faure added a comment - @oleg.pronchenko https://stackoverflow.com/questions/13017931/disabling-jira-notification-emails-for-rest-api-updates/13025457?noredirect=1#comment89310388_13025457 says you need ProjectAdmin or Admin rights for notifyUsers=false to work. For some reason.

            Hi everyone

            PUT /rest/api/2/issue/{issueIdOrKey}/worklog/{id}?notifyUsers=false

            notifyUsers parameter does not work. The notification to email always come

            Jira v7.12.0

            oleg.pronchenko added a comment - Hi everyone PUT /rest/api/2/issue/{issueIdOrKey}/worklog/{id}?notifyUsers=false notifyUsers parameter does not work. The notification to email always come Jira v7.12.0

            dmeyer, the com.atlassian.jira.rest.v2.issue.IssueAttachmentsResource#addAttachment method has the following line:

                        issueUpdateBean.setDispatchEvent(true);
            

            which sends a notification whenever an attachment is added through the REST API. This notification should be optional.

            I have created https://ecosystem.atlassian.net/browse/ACJIRA-1403 for that.

            David

            David Fischer added a comment - dmeyer , the com.atlassian.jira.rest.v2.issue.IssueAttachmentsResource#addAttachment method has the following line: issueUpdateBean.setDispatchEvent( true ); which sends a notification whenever an attachment is added through the REST API. This notification should be optional. I have created https://ecosystem.atlassian.net/browse/ACJIRA-1403 for that. David

            NOTE: We are using https://docs.atlassian.com/jira/REST/7.2.1/#api/2/issue/\{issueIdOrKey}/attachments , not sure what other API's might be out there, in case a different one causes it.

            Robert Zaleski added a comment - NOTE: We are using  https://docs.atlassian.com/jira/REST/7.2.1/#api/2/issue/\ {issueIdOrKey}/attachments , not sure what other API's might be out there, in case a different one causes it.

            kk added a comment -

            I second Robert's comment: JIRA does send e-mails for REST-based attachment actions.

            kk added a comment - I second Robert's comment: JIRA does send e-mails for REST-based attachment actions.

            What generates the e-mail below then?

             

            TaxSys Software / Development TS-42627
            Add a link to upload roll files
            Change By: Gitc User
            Attachment: TS-42627-visual_sparks_output.txt
            Add Comment Add Comment

            This message was sent by Atlassian JIRA (v7.2.1#72003-sha1:3448e6b)

            Robert Zaleski added a comment - What generates the e-mail below then?   TaxSys Software / Development TS-42627 Add a link to upload roll files Change By: Gitc User Attachment: TS-42627-visual_sparks_output.txt Add Comment Add Comment This message was sent by Atlassian JIRA (v7.2.1#72003-sha1:3448e6b)

              Unassigned Unassigned
              73f0b2e75f82 Sorin Sbarnea (Citrix)
              Votes:
              135 Vote for this issue
              Watchers:
              111 Start watching this issue

                Created:
                Updated:
                Resolved: