Updating a 'published' page to 'draft' status using REST API v2 with 'PUT Update page' causes multiple errors

XMLWordPrintable

    • Minor

      Issue Summary

      The new API feature to update drafts of pages with change Confluence Cloud changelog should allow the ability to Update the Status of a page from ‘Current’ to ‘Draft’, this information can be found here - The Confluence Cloud REST API :

      The new version of the updated page. Set this to the current version number plus one, unless you are updating the status to 'draft' which requires a version number of 1.

      So going by the documentation, it should allow the Current published page to update to Draft status, though instead, it is making a copy of the current page as a Draft.

       

      Another issue is, the payload that is sent that changes the Title, Body etc of the page is updated with a 200 response and the body returned is correct. Then when going to the actual UI you first see the correct name of the updated draft:

      Though clicking through takes you to the draft page with the ‘Current’ content (note: the updated content from the API call is shown for ~.2 secs then reverts to original):

      Steps to Reproduce

      1. Make a PUT call on endpoint /wiki/api/v2/pages/{id} where {{ {id}

        }} is a published page

      2. In the body of the request, make sure the version number is 1 and status is ‘draft’
      3. Check UI to see the above in action

      Expected Results

      The published page becomes a draft with the new content provided in the API call

      Actual Results

      The published page is Duplicated to a draft and once opened, contains the original, un-updated content. Also, this draft page can not be deleted.

      Workaround

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

            Assignee:
            Miyo Imai
            Reporter:
            Joshua Zarazovski (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: