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

Confluence Userkey/AccountIDs in body.storage response

      Issue Summary

      We’re in the process of migrating our Confluence app. We’ve previously relied on the body.storage response from /wiki/rest/api/content/{id} which returns the page content in XML format. In there, we look for <ri:user ri:userkey=“8a7f808360575f7501606910dc1600cb” /> tags to identify users when they are mentioned.

      These tags are not updated to use Account IDs when calling the REST API with the privacyMode flag and updating the apiMigrations gdpr flag in the descriptor. Do you have any plans to update the body.storage XML or is there another way to get mentions in a Confluence page with Account IDs?

      Notes

      Workaround

      The body.editor2 format seems to return tags including an Atlassian Account ID. Should we use those instead? On https://developer.atlassian.com/cloud/confluence/rest/#api-content-post it is mentioned that “Note, editor2 format is used by Atlassian only.” and I want to make sure we don’t have to do another migration anytime soon.

          Form Name

            [CONFCLOUD-66214] Confluence Userkey/AccountIDs in body.storage response

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!

            Sunny Xu (Inactive) added a comment - Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team!

            cc ssreenivasan since this is related to GDPR. 

            Soum Ghoshal added a comment - cc  ssreenivasan  since this is related to GDPR. 

              Unassigned Unassigned
              7d9ae0d87192 Ben Romberg - codefortynine
              Affected customers:
              1 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: