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

Improve notification when moving a Hierarchy including Restricted pages to a new Space

    • 0
    • 1
    • 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.

      Problem Definition

      The current versions of Confluence behave as follows.

      1. There are two users on Confluence
        • User A
        • User B
      2. There is the following page tree in a space
        • Parent
          • Child 1 (No restriction)
          • Child 2 (Restricted to User A)
      3. User B moves "Parent" page including the children to another space
      4. As User B can see only "Parent" page and "Child 1" page, the pages are moved to the new space and "Child 2" page is left over in the old space with no parent.

      User B may break the page hierarchy unintentionally in the above situation.

      Suggested Solution

      It would be nice if Confluence could show any notification/warning to User B in the above situation.

            [CONFSERVER-12722] Improve notification when moving a Hierarchy including Restricted pages to a new Space

            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

            Yuki Okamoto (Inactive) added a comment - - edited

            I updated the description and kept the original one as follows.

            Original Description

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

            Pages with restrictions need to be left behind so they don't get moved to a space where they are no longer valid. But it would be nice if there was some sort of notification to the System Administrator when they move a hierarchy that would result in pages being left behind.

            EDITED

            1. Create a child page, pageA, within spaceA and set it up so only userA can view/edit it.
            2. Log in as spaceAadmin and move an entire tree of pages, that would normally include pageA, to spaceB

            The above results in pageA being left hidden, only viewable/editable by userA, in spaceA.

            Now, if spaceAadmin looks at the Restricted Pages tab on spaceA, he will see pageA exists with restrictions but there is no way to tell that this page was actually left behind. It would be nice if I this case of restricted pages being left behind, there should atleast be a red flag of some sort posted to the mover if he is a Space Admin.
             

            Yuki Okamoto (Inactive) added a comment - - edited I updated the description and kept the original one as follows. Original Description NOTE: This suggestion is for Confluence Server . Using Confluence Cloud ? See the corresponding suggestion . Pages with restrictions need to be left behind so they don't get moved to a space where they are no longer valid. But it would be nice if there was some sort of notification to the System Administrator when they move a hierarchy that would result in pages being left behind. EDITED Create a child page, pageA, within spaceA and set it up so only userA can view/edit it. Log in as spaceAadmin and move an entire tree of pages, that would normally include pageA, to spaceB The above results in pageA being left hidden, only viewable/editable by userA, in spaceA. Now, if spaceAadmin looks at the Restricted Pages tab on spaceA, he will see pageA exists with restrictions but there is no way to tell that this page was actually left behind. It would be nice if I this case of restricted pages being left behind, there should atleast be a red flag of some sort posted to the mover if he is a Space Admin.  

            Maleko

            Thanks for the issue report, I have edited and expanded your description. The Complexity and Value have been set so it can be scheduled.

            Cheers
            Matt

            m@ (Inactive) added a comment - Maleko Thanks for the issue report, I have edited and expanded your description. The Complexity and Value have been set so it can be scheduled. Cheers Matt

              barconati BillA
              mtaylor@atlassian.com Maleko Taylor (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: