EPIC Goal

Enables user ownership resolution to include indirect group memberships (parent group of the group the user is directly a member of. This should work with RBAC.

Background/Feature Origin

More context in this bug: https://issues.redhat.com/browse/RHDHBUGS-130

Why is this important?

It covers a use case that was previously not considered and not tested.

User Scenarios

Parent team: feature

• Doesn't actually have any members and it’s used to contain sub team
• owns sub team feature-admin, and feature-dev
• current behaviour: if the owner of a component in feature, the sub teams will not have access to it because the sub teams are not in direct ownership

Dependencies (internal and external)

Acceptance Criteria

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>