Details
-
Bug
-
Resolution: Timed out
-
Low
-
Severity 2 - Major
-
Description
I am calling
https://MY_TENANT.atlassian.net/wiki/rest/api/content/MY_PAGE_ID
with this content:
{"id":"SOMEID","type":"page","title":"better retros GDPR 1","space": {"key":"SAS"} ,"version":\{"number":2,"minorEdit":false},"body":{"storage": {"value":"<ac:layout><ac:layout-section ac:type=\"single\"><ac:layout-cell><ac:structured-macro ac:name=\"details\"><ac:rich-text-body><table><tbody><tr><th>Date</th><td><time datetime=\"2019-03-05\" /></td></tr><tr><th>Participants</th><td><p><ac:link><ri:user ri:accountId=\"CLOUD_ID\"/></ac:link></p><p><ac:link><ri:user ri:accountId=\"CLOUD_ID\"/></ac:link></p></td></tr></tbody></table></ac:rich-text-body></ac:structured-macro></ac:layout-cell></ac:layout-section><ac:layout-section ac:type=\"two_equal\"> <ac:layout-cell><ac:structured-macro ac:name=\"panel\"><ac:parameter ac:name=\"borderColor\">#36B37E</ac:parameter><ac:parameter ac:name=\"bgColor\">#ABF5D1</ac:parameter><ac:rich-text-body><h3>The Good</h3></ac:rich-text-body></ac:structured-macro><ul><li>asd (0 votes)</li><li>asd (0 votes)</li></ul></ac:layout-cell><ac:layout-cell><ac:structured-macro ac:name=\"panel\"><ac:parameter ac:name=\"borderColor\">#FF5630</ac:parameter><ac:parameter ac:name=\"bgColor\">#FFBDAD</ac:parameter><ac:rich-text-body><h3>The Bad</h3></ac:rich-text-body></ac:structured-macro><ul><li>asd (0 votes)</li><li>asdasd (0 votes)</li></ul></ac:layout-cell> </ac:layout-section></ac:layout>","representation":"storage"} }}
Focus on `<ri:user ri:accountId=\"CLOUD_ID\"/>` part.
https://developer.atlassian.com/cloud/confluence/api-changes-for-user-privacy-announcement/
This page says I can use it this way.
AND it referes to this issue: https://jira.atlassian.com/browse/CONFCLOUD-59872?_ga=2.25119290.1486699399.1551658336-1590635113.1541027003
which marked as resolved.
But I get 500.
- Why is it 500? When according to an error I am using API incorrectly? It should be at least 400.
- This blocks me from moving to GDPR world.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available