• 5
    • 3
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Background

      • In an enterprise environment or an environment with many users, pages are constantly moved from one location to another (either from one parent page to another within one space or from one space to another space)
      • These movements should be recorded as part of the page history to allow users to reconcile the complete history of a page
      • IMHO the former location of a page belongs to - according to my definition of - "full page history"

      Exemplary Use Case

      • A Confluence page contains critical or sensible information ("Critical Page")
      • For compliance reasons the question arises whether or not this Critical Page was at any point in time located in eg. an unprotected space
      • In order to validate this, a record of the page's movement should be added to the page history
      • Put differently: it is not sure that a page that is now located in the "correct" space always was there; it could well be that the page was formerly accessible in a different space and only recently moved to the "correct" space

            [CONFSERVER-27103] Movement of a page should be recorded in page history

            Vebloud added a comment -

            I consider this a bug not an enhancement. Someone can come to my page and just move it around without a trace? Seriously, it makes Confluence absolutely unusable for any documentation where changes has to be tracked and potentially undergo audit.

            Vebloud added a comment - I consider this a bug not an enhancement. Someone can come to my page and just move it around without a trace? Seriously, it makes Confluence absolutely unusable for any documentation where changes has to be tracked and potentially undergo audit.

            a page's location/movement (provenance) is definitely part of the history and can be equally as important as did the content change or was the format updated.  Location can change the entire context of the page and must be considered an important change worth of logging.

            Jon Schmidt added a comment - a page's location/movement (provenance) is definitely part of the history and can be equally as important as did the content change or was the format updated.  Location can change the entire context of the page and must be considered an important change worth of logging.

            agreed, please reconsider this essential feature 

            gary carter added a comment - agreed, please reconsider this essential feature 

            Please reconsider not developing this feature. It's needed to track who moved what and understand where a page belonged if a user moved it by accident. 

            Elle Taylor added a comment - Please reconsider not developing this feature. It's needed to track who moved what and understand where a page belonged if a user moved it by accident. 

            Page location history is I would feel quite an important feature to ensure there is accountability and traceability for content. Knowing who moved a page, and from where the page was moved are invaluable information to have. Please reconsider implementing this issue, as it is clearly an strongly requested feature.

            Also related to https://jira.atlassian.com/browse/CONFSERVER-5231

            Matt Keenan added a comment - Page location history is I would feel quite an important feature to ensure there is accountability and traceability for content. Knowing who moved a page, and from where the page was moved are invaluable information to have. Please reconsider implementing this issue, as it is clearly an strongly requested feature. Also related to https://jira.atlassian.com/browse/CONFSERVER-5231

            Jens added a comment -

            At least here is some reaction, not like on the other tickets from year 2006 and so on.. anyway how difficult could be to do such a thing.. or meet the needs of customers..

            Jens added a comment - At least here is some reaction, not like on the other tickets from year 2006 and so on.. anyway how difficult could be to do such a thing.. or meet the needs of customers..

            Yeah, it will be quite interesting

            Gonchik Tsymzhitov added a comment - Yeah, it will be quite interesting

            So pages can be moved around and nobody knows who did it.

            Makes perfect sense to me. Content management isn't really important anyway.

            David Sumlin added a comment - So pages can be moved around and nobody knows who did it. Makes perfect sense to me. Content management isn't really important anyway.

            Thanks for your interest in this issue.

            While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future.

            This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.

            Cheers,

            Confluence Product Management

            Adam Barnes (Inactive) added a comment - Thanks for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. Cheers, Confluence Product Management

            Andreas van Rienen added a comment - - edited

            Andreas van Rienen added a comment - - edited In this regard, CONF-24547 and CONF-19721 are also very relevant as well.

              Unassigned Unassigned
              3b2156fb5ad7 Andreas van Rienen
              Votes:
              88 Vote for this issue
              Watchers:
              54 Start watching this issue

                Created:
                Updated: