Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-22313

Allow for adding or removing a Space Watch on behalf on another user

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

      Confluence administrators (globally) and spaces administrators (for their spaces) should be able to add or remove a space watch on behalf of another user. This is key in teams where new people come onboard and the team leader wants them to keep up to date with what's going on without waiting for them to learn about how notifications work in Confluence.

      Within the UI, this can be done in "Manage Watchers" by adding this feature to the "Watching this space" as is exists for "Watching this page" (instead of "You cannot modify this list").

      It needs to be added to the API as well, as watchSpace will only work for the authenticated user.

      N.B. this is NOT a duplicate of CONF-5866 as there is still no way to add or remove a space watch for another user.

          Form Name

            [CONFSERVER-22313] Allow for adding or removing a Space Watch on behalf on another user

            The safest way to do this (as an admin) is via the REST API: https://docs.atlassian.com/ConfluenceServer/rest/7.12.3/#api/user/watch

             

            Richard Cross added a comment - The safest way to do this (as an admin) is via the REST API: https://docs.atlassian.com/ConfluenceServer/rest/7.12.3/#api/user/watch  

            Penny Boulet added a comment - - edited

            This is still a problem in Confluence 7.4.0

            Found this as a workaround. ICK

            https://confluence.atlassian.com/confkb/user-cannot-stop-watching-pages-941621041.html

            Penny Boulet added a comment - - edited This is still a problem in Confluence 7.4.0 Found this as a workaround. ICK https://confluence.atlassian.com/confkb/user-cannot-stop-watching-pages-941621041.html

            This issue is mentioned in commits included in the Confluence 6.0.0-OD-2016.01.1-0003 release being approved for production: CPU-180

            Deleted Account (Inactive) added a comment - This issue is mentioned in commits included in the Confluence 6.0.0-OD-2016.01.1-0003 release being approved for production: CPU-180

            This issue is mentioned in commits included in the Confluence 6.0.0-OD-2016.01.1-0002 release being approved for production: CPU-179

            Deleted Account (Inactive) added a comment - This issue is mentioned in commits included in the Confluence 6.0.0-OD-2016.01.1-0002 release being approved for production: CPU-179

            This issue is mentioned in release Confluence 6.0.0-OD-2015.52.1-0001 just promoted to jirastudio-prd-virtual

            Deleted Account (Inactive) added a comment - This issue is mentioned in release Confluence 6.0.0-OD-2015.52.1-0001 just promoted to jirastudio-prd-virtual

            This issue is mentioned in commits included in the Confluence 6.0.0-OD-2015.52.1-0001 release being approved for production: CPU-171

            Deleted Account (Inactive) added a comment - This issue is mentioned in commits included in the Confluence 6.0.0-OD-2015.52.1-0001 release being approved for production: CPU-171

            I know this is just getting ready to merge in, but does this also allow for adding / removing "Watch all new blog posts in a Space" on behalf of another user?

            Ian Lee [LLNL] added a comment - I know this is just getting ready to merge in, but does this also allow for adding / removing " Watch all new blog posts in a Space " on behalf of another user?

            Glad you guys are working on this!

            Scott Paden added a comment - Glad you guys are working on this!

            Drew, you are a star! Looking into it, thanks

            Jonas Andersson added a comment - Drew, you are a star! Looking into it, thanks

            Drew Bentley added a comment - - edited

            Jonas,

            It's going to be under the NOTIFICATIONS table. You'll need to get their NOTIFICATIONSID to remove.

            I ran into this issue with disabled users still as watchers. This is the query I used to find disabled users who were still space watchers:

            mysql> use confluence;
            mysql> select c.spacename, b.display_name, a.*  from NOTIFICATIONS a inner join cwd_user b on a.username = b.user_name and b.active = 'F' inner join SPACES c on a.spaceid = c.spaceid  where a.pageid is null and a.spaceid is not null;
            

            Once I got their ID, I then ran:

            mysql> delete from NOTIFICATIONS where NOTIFICATIONID = 7667798;
            

            At least that is what I found in my history. With a little query changes, you should be able to query the spacename you want and then get the userid's in it you want to remove.

            I suggest making a mock database and site first to test any manual deletions.

            Cheers,

            -Drew

            Drew Bentley added a comment - - edited Jonas, It's going to be under the NOTIFICATIONS table. You'll need to get their NOTIFICATIONSID to remove. I ran into this issue with disabled users still as watchers. This is the query I used to find disabled users who were still space watchers: mysql> use confluence; mysql> select c.spacename, b.display_name, a.* from NOTIFICATIONS a inner join cwd_user b on a.username = b.user_name and b.active = 'F' inner join SPACES c on a.spaceid = c.spaceid where a.pageid is null and a.spaceid is not null; Once I got their ID, I then ran: mysql> delete from NOTIFICATIONS where NOTIFICATIONID = 7667798; At least that is what I found in my history. With a little query changes, you should be able to query the spacename you want and then get the userid's in it you want to remove. I suggest making a mock database and site first to test any manual deletions. Cheers, -Drew

              jmcarthur James McArthur (Inactive)
              dbaf23462600 François Nonnenmacher
              Affected customers:
              227 This affects my team
              Watchers:
              146 Start watching this issue

                Created:
                Updated:
                Resolved: