Child does not inherit parent's Resource Group

[wshawn]

wshawn created Redmine issue ID 4601

Should their be an automatic inheritance of parent's resource group or at least a notification that a group has been applied to the parent.

My thinking is a document may be directly accessible even though the parent is not, when this is probably not the desired implementation.

If a container is added to the Resource Group, should that not also inherit downwards without having to add each of the documents to the "Resource Group" manually?

[SebastienDaniel]

afaik, this isn't a bug. It's by design.
However, I can't recall the justification of this design and it is a frequent source of debate.

[pixelchutes]

A new child does inherit a parent's Resource Groups upon creation, at least since #11301 (and used to in Evo).

As far as drag & drop / updating parent for an individual Resource or a container (w/ multiple Resources), that's definitely a questionable scenario. A pre-existing Resource may already have all necessary permissions, or intentionally no permissions at all. It seems the best option would be to offer a choice to the user.

I can see the benefit to both sides (auto-inherit vs. not), and ideally would somehow be an option applicable on-the-fly vs. a system-wide setting, e.g. all or nothing.

[wshawn]

This is indeed corrected.