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

      Support nested groups management via the Confluence UI

      Example:
      Group: PARENTGROUP contains user: A, B, and C. However, we want to add all of the users from another group, ANOTHERGROUP to the PARENTGROUP. Therefore, if ANOTHERGROUP had users: D, E, F, and G, making ANOTHERGROUP a subgroup of PARENTGROUP would give PARENTGROUP users A, B, C, D, E, F, and G. Though logically Confluence could display the idea of a "subgroup", the core functionality of this subgroup feature would be the ability to merge group members from different groups when needed. Likewise, whenever the time came to remove the subgroup, the "remove selected subgroup" feature would take all members associated with that subgroup out of the parent group. In context with the example above, PARENTGROUP, after removing ANOTHERGROUP from being its subgroup would only contain users A, B, and C again.

            [CONFSERVER-20902] Supported nested groups management in the Confluence UI

            BillA added a comment -

            Thank you for raising this issue. While we can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea.

            BillA added a comment - Thank you for raising this issue. While we can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea.

            linked to nested group support

            Sherif Mansour added a comment - linked to nested group support

            Renamed issue title

            Sherif Mansour added a comment - Renamed issue title

            Sherif

            Users in our Confluence instance are from LDAP, but since our LDAP groups
            are not well organized in AD for Confluence, I have created my own
            Confluence groups to organize our LDAP users. So, the answer to your first
            question is 'Confluence groups'. Second, CONF-17150 is exactly what I'm
            talking about. Unfortunately, for us the implementation would need to be
            done in the system rather in LDAP. Thank you for your time!

            Eddie

            On Fri, Oct 8, 2010 at 5:52 PM, Sherif Mansour [Atlassian] (JIRA) <


            Ed Connatser | IT Developer | Burris Logistics
            501 SE 5th Street, Milford, DE 19963 | econnatser@burrislogistics.com
            D: 302.839.5146 | www.burrislogistics.com

            This electronic message and all contents and attachments contain information
            from Ed Connatser, Confluence Developer of Burris Logistics that may be
            privileged, confidential or otherwise protected from disclosure. The
            information is intended to be for the addressee only. If you are not the
            addressee, then any disclosure, copy, distribution or use of this message or
            its contents or any of its attachments is prohibited. If you have received
            this electronic message in error, please notify me immediately and destroy
            the original message and all copies.

            Eddie Connatser added a comment - Sherif Users in our Confluence instance are from LDAP, but since our LDAP groups are not well organized in AD for Confluence, I have created my own Confluence groups to organize our LDAP users. So, the answer to your first question is 'Confluence groups'. Second, CONF-17150 is exactly what I'm talking about. Unfortunately, for us the implementation would need to be done in the system rather in LDAP. Thank you for your time! Eddie On Fri, Oct 8, 2010 at 5:52 PM, Sherif Mansour [Atlassian] (JIRA) < – Ed Connatser | IT Developer | Burris Logistics 501 SE 5th Street, Milford, DE 19963 | econnatser@burrislogistics.com D: 302.839.5146 | www.burrislogistics.com This electronic message and all contents and attachments contain information from Ed Connatser, Confluence Developer of Burris Logistics that may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee only. If you are not the addressee, then any disclosure, copy, distribution or use of this message or its contents or any of its attachments is prohibited. If you have received this electronic message in error, please notify me immediately and destroy the original message and all copies.

            Eddie,
            Couple of questions - are your groups in LDAP or do you want them to be in Confluence? Also, does CONF-17150 cover what you are after?
            I'm thinking something this complex should belong in LDAP not in the product...
            Sherif

            Sherif Mansour added a comment - Eddie, Couple of questions - are your groups in LDAP or do you want them to be in Confluence? Also, does CONF-17150 cover what you are after? I'm thinking something this complex should belong in LDAP not in the product... Sherif

              Unassigned Unassigned
              527feab301ff Eddie Connatser
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: