Bug 1739333

Summary: sub-team member doesnt have edit rights
Product: [Community] Bugzilla Reporter: Jeff Fearn 🐞 <jfearn>
Component: ExtensionsAssignee: Jeff Fearn 🐞 <jfearn>
Extensions sub component: Manage Components QA Contact: Lianghui Yu <liyu>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: unspecified    
Priority: unspecified CC: liyu
Version: 5.0   
Target Milestone: 5.0-RH7   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.0.4-rh29 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-10 22:20:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeff Fearn 🐞 2019-08-09 04:35:34 UTC
Description of problem:
Someone who is only a member of a sub-team does not have edit rights on a component with a default pool from another team.

Version-Release number of selected component (if applicable):
5.0

How reproducible:
Easy

Steps to Reproduce:
1. Set up default pool as a pool from Team A
2. Add team B as sub-team
3. visit component management page as someone who is in team B and not in team A

Actual results:
User cannot edit their components

Expected results:
User can edit their components.

Additional info:
If the default pool isn't set or the user is a member of team A, then they will be able to edit.

Comment 1 Lianghui Yu 2019-08-09 06:01:18 UTC
A user with sub team membership is able to edit the attributes, And those users can actually edit sub team as well.
It results user to ban themself from further edit that component, privilege is checked when save, so not a big issue.
Result: PASS

Comment 3 Jeff Fearn 🐞 2019-09-08 22:18:49 UTC
This change has been deployed to the pre-production infrastructure at https://partner-bugzilla.redhat.com

Comment 4 Jeff Fearn 🐞 2019-09-10 22:20:09 UTC
This change is now live. If there are any issues, do not reopen this
bug. Instead, you should create a new bug and reference this bug.