Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-38804

Add ability to disable 'Notify Watcher' in Confluence REST API

XMLWordPrintable

    • 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

            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.

            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.

            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.

            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.

            Martin Papproth added a comment -

            This would be very helpful for us, too.

            Can you implement the same solution as in JIRA, please ?

            https://jira.atlassian.com/browse/JRA-34423

             

            Martin Papproth added a comment - This would be very helpful for us, too. Can you implement the same solution as in JIRA, please ? https://jira.atlassian.com/browse/JRA-34423  

            John Jones added a comment -

            We have a reporting tool that uploads customer analytics once a month. My work-around for the problem described in this ticket is to have the reporting tool upload to my personal space, and I then have to manually move it to the shared space. Otherwise everyone in our company gets hundreds of emails from me once a month and the less technical members of our company seemed to think this is something I do out of spite for them.
            Please fix the API. :<

            John Jones added a comment - We have a reporting tool that uploads customer analytics once a month. My work-around for the problem described in this ticket is to have the reporting tool upload to my personal space, and I then have to manually move it to the shared space. Otherwise everyone in our company gets hundreds of emails from me once a month and the less technical members of our company seemed to think this is something I do out of spite for them. Please fix the API. :<

            Edward C. Skoviak added a comment -

            Any chance this work will be done? We maintain inventory pages that are frequently updated via the REST API and likewise this is generating a lot of noise for us.

            Edward C. Skoviak added a comment - Any chance this work will be done? We maintain inventory pages that are frequently updated via the REST API and likewise this is generating a lot of noise for us.

            Andy Earnshaw added a comment -

            We're in the process of migrating a lot of documentation to confluence. It's generated and then deployed using the REST API, and there are many pages involved. Every time we update and deploy this documentation, any watchers for that space get 1 email per updated page, which is extremely annoying. It would be nice if we could batch deploy these updates and then just send one notification out to watchers.

            Is there a workaround possible?

            Andy Earnshaw added a comment - We're in the process of migrating a lot of documentation to confluence. It's generated and then deployed using the REST API, and there are many pages involved. Every time we update and deploy this documentation, any watchers for that space get 1 email per updated page, which is extremely annoying. It would be nice if we could batch deploy these updates and then just send one notification out to watchers. Is there a workaround possible?

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

                Created:
                Updated: