Uploaded image for project: 'JIRA Server (including JIRA Core)'
  1. JIRA Server (including JIRA Core)
  2. JRASERVER-34423

Add the ability to update issues via REST without sending notifications

    Details

    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      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

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ssbarnea Sorin Sbarnea (Citrix)
              • Votes:
                135 Vote for this issue
                Watchers:
                101 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: