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

Page History versions aren't reordered/renamed when deleting an intermediary page version

      Issue Summary

      • When deleting a page version, on the Page History page, that is an intermediary page version, it won't be renamed/reordered up on the versions list, keeping its original version.

      Steps to Reproduce

      1. Create a page in Confluence
      2. Edit this page at least 3 times
      3. Having, for example, 3 versions of the page, navigate to the Page History of the affected page
        • Numbering scheme:
          1. v1
          2. v2
          3. v3
      4. Delete version 2 of the page

      Expected Results

      • Version 1 should remain being v1, and version 3 should now be the v2.
      • Numbering scheme:
        1. v1
        2. v2

      Actual Results

      • Version 1 remains being v1, but version 3 keeps being v3 instead of v2:
      • Numbering scheme:
        1. v1
        2. v3

      Workaround

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

          Form Name

            [CONFSERVER-61228] Page History versions aren't reordered/renamed when deleting an intermediary page version

            A fix for this issue is available to Server and Data Center customers in Confluence 7.12.0
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            Franco Skrzypczak added a comment - A fix for this issue is available to Server and Data Center customers in Confluence 7.12.0 Upgrade now or check out the Release Notes to see what other issues are resolved.

            Fixed shipped in 7.11.2

            Dylan Rathbone added a comment - Fixed shipped in 7.11.2

            Steve Hadfield added a comment - - edited

            This affects our version because we used the ScriptRunner for Confluence's Prune Old Page Versions, which has caused issues in our database that desparately need to be corrected ASAP. I've been waiting for this fix to be implemented to "fix" my database and be able to continue using the ScriptRunner for Confluence's Prune Old Page Versions job. This fix needs to be in 7.13, the enterprise version. I need 7.11 for the new metrics addition. This is super important for my instance as it move to Azure.

            And the impact of this issue is major - to those that have OS_PROPERTYENTRY tables messed up because of this issue.

            Steve Hadfield added a comment - - edited This affects our version because we used the ScriptRunner for Confluence's Prune Old Page Versions, which has caused issues in our database that desparately need to be corrected ASAP. I've been waiting for this fix to be implemented to "fix" my database and be able to continue using the ScriptRunner for Confluence's Prune Old Page Versions job. This fix needs to be in 7.13, the enterprise version. I need 7.11 for the new metrics addition. This is super important for my instance as it move to Azure. And the impact of this issue is major - to those that have OS_PROPERTYENTRY tables messed up because of this issue.

            Jonny Carter added a comment - - edited

            As a side note, this will also affect any third party applications using Atlassian's PageService API to remove old page versions.

            In my case, that affects ScriptRunner for Confluence's Prune Old Page Versions job.

            Jonny Carter added a comment - - edited As a side note, this will also affect any third party applications using Atlassian's PageService API to remove old page versions . In my case, that affects ScriptRunner for Confluence's Prune Old Page Versions job.

              b56a0fbdbbcd Dylan Rathbone
              rbueno Renata Bueno
              Affected customers:
              9 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: