What can be done with this module that can't be done with subgroup?

Created on 22 May 2023, about 1 year ago
Updated 20 June 2024, 5 days ago

Problem/Motivation

I'm not sure if I got the difference..
My speculation: with ggroup (this module) you can have a co-manager of a child group (ggroup) that is not a member of the parent group, while you can't in a subgroup

Therefore please confirm if I'm right and document a bit more (with a usecase example) what can be done with this module that can't be done with subgroup, so that I can better decide which one of the 2 to support 😊🙏🏻

💬 Support request
Status

Fixed

Version

3.0

Component

Documentation

Created by

🇮🇹Italy kopeboy Mainland

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @kopeboy
  • 🇧🇪Belgium LOBsTerr

    1) The way modules build the tree is build
    2) Subgroup (tree) by default propagate roles to subgroups and I think there is no way to disable it
    3) Subgroup (graph current module), by default doesn't provide you any propagation or inheritance of the roles, but there is a ticket, which allows to get role mappings between parent and child group. Currently I came back to development and my idea to include patch to the module.
    4) Subgroup (tree): I also believe there are some limitations with group types, you can use it between different trees.
    5) Subgroup (graph current module), no limitations, except of cause loops!

    Maybe it is better to write down you requirements and ask based on them.
    It would be much easier to understand, what is missing.

  • Status changed to Fixed 19 days ago
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.69.0 2024