Copying a page with JSON custom content properties does not copy properties

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      The fix for this bug has been released to our Long Term Support release.

      The fix for this bug is now available in the latest release of Confluence 7.13 and 7.19

      Issue Summary

      When copying a page that has custom content as a JSON property, the custom content is not copied.

      See Content properties in the REST API for accessing content properties via REST.

      This can also occur when using ContentPropertyService with JsonContentProperty

      Steps to Reproduce

      1. Create a page in Confluence
      2. Add JSON page properties with (using new page contentId)
        curl --user admin:admin --verbose --silent --request POST "http://localhost:1990/confluence/rest/api/content/<contentId>/property" --header 'Content-type: application/json' --data-raw '
        {
            "key":"test-key",
            "value": "test-value"
        }' | jq '.'
      3. Copy page with ... -> Copy page
      4. Check new page properties with
        curl --user admin:admin --verbose --silent --request GET "http://localhost:1990/confluence/rest/api/content/<newContentId>/property" | jq '.'
        

      Expected Results

      The page properties are returned in the JSON response.

      Actual Results

      The page properties are not returned.

      {
        "results": [],
        "start": 0,
        "limit": 10,
        "size": 0,
        "_links": {
          "self": "http://localhost:1990/confluence/rest/api/content/<newContentId>/property",
          "base": "http://localhost:1990/confluence",
          "context": "/confluence"
        }
      } 

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Quan Pham
            Reporter:
            James Richards
            Votes:
            6 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: