• 1
    • 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Problem Definition

      The SOAP API (XML/RPC) had a minor revision element that could be set to true in order to disable notify watcher. There is no equivalent in the REST API, so any mass updates performed using the REST API will spam Confluence users.

      Suggested Solution

      3 possibly solutions:

      • Add an argument that can be used in the REST request to disable Notify Watchers
      • Set the default behavior when using REST to disable Notify Watchers
      • Add a setting in the Confluence administration panel to either enable or disable Notify Watchers when using Remote APIs

      Workaround

      There is no workaround. Any mass edits performed using the REST API will send notifications to watchers.

            [CONFCLOUD-38804] Add ability to disable 'Notify Watcher' in Confluence REST API

            We are about to mass create/update several hundred pages, where we will be @-tagging users.

            Without a "don't send notifications" option that can be provided in the API call we'll probably be sending out a couple of thousand emails.

            Rune Rasmussen added a comment - We are about to mass create/update several hundred pages, where we will be @-tagging users. Without a "don't send notifications" option that can be provided in the API call we'll probably be sending out a couple of thousand emails.
            SET Analytics Bot made changes -
            UIS New: 1

            Came here to say that it is very disappointing that this issue is marked "not being considered" wthout giving any explanation or proposing a workaround.

            Dominik Fischer added a comment - Came here to say that it is very disappointing that this issue is marked "not being considered" wthout giving any explanation or proposing a workaround.
            Takuya Nagasaka (Inactive) made changes -
            Remote Link Original: This issue links to "HOT-83192 (Atlassian Service Operations JIRA )" [ 355655 ] New: This issue links to "HOT-83192 (Atlassian Service Operations JIRA)" [ 355655 ]
            Giuliano C. made changes -
            Security Original: Atlassian Staff [ 10750 ]
            Peter Obara made changes -
            PM Reviewed New: 24/Jan/2022
            Status Original: Gathering Interest [ 11772 ] New: Not Being Considered [ 11776 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3420018 ] New: JAC Suggestion Workflow 3 [ 3616672 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2247014 ] New: JAC Suggestion Workflow [ 3420018 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            SET Analytics Bot made changes -
            Support reference count New: 2
            Megha made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 357257 ]

              Unassigned Unassigned
              sbrannen@atlassian.com Branno (Inactive)
              Votes:
              27 Vote for this issue
              Watchers:
              25 Start watching this issue

                Created:
                Updated: