Bug 116108 - Cannot add Member to Role
Summary: Cannot add Member to Role
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: ui   
(Show other bugs)
Version: nightly
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Scott Seago
QA Contact: Daniel Berrange
URL: http://youth.aplaws.org.uk/ccm/conten...
: 116115 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2004-02-18 11:19 UTC by James Kearns
Modified: 2008-10-06 13:39 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-06 13:39:04 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description James Kearns 2004-02-18 11:19:48 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:

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

How reproducible:

Steps to Reproduce:
1. Log in with Site Wide Administrator group permissions.
2. Go to Roles tab. Select "First Time Author" role.  
3. Click "Add member". Use Search. Tick "content Administration First 
Time Author" from results. 
4. Click "Add Members" button.

Actual Results:  An unexpected error has occurred.

Expected Results:  Automatically returned to Role details screen.
"content Administration First Time Author" now appears in Members 

Additional info:

Can achieve expected results with other members, for 
example, "Heather Fishlock"

Comment 1 Daniel Berrange 2004-02-18 11:26:10 UTC
'content Administration First Time Author' is in fact the internal
name for the 'First Time Author' role. So what you are attempting to
do here is to add the role to itself - which causes CMS to throw an
error. That said, CMS should not have listed this role for you when
doing the search in the first place. Thus the fix we'll apply is to
filter out these roles when doing the search

Comment 2 Daniel Berrange 2004-02-18 11:53:06 UTC
*** Bug 116115 has been marked as a duplicate of this bug. ***

Comment 3 James Kearns 2004-02-18 11:55:59 UTC
'content Administration First Time Author' is a Group I set up.

Comment 4 Scott Seago 2004-02-18 14:35:39 UTC
Actually, we should only filter out the current role. It should be
possible to add "content administration Author" to the editor role, as
a  shortcut for making sure the same users are assigned to both roles,
in cases where that is desirable.

But yes, in this case, you were attempting to add a group to itself,
which would definitely fail. The UI should, at a minimum, filter out
the current group and all supergroups. i.e. if the content section is
"content", the role is "Author", then the system creates the "content
Administration" group which is the supergroup for all roles in the
content section, and for the "Author" role the group "content
Administration Author" is created to contain the assigned users/groups
for the role. Both of these groups should be filtered out, but
"content Administration Editor" should probably remain in the list.

Comment 5 Scott Seago 2004-02-18 16:49:27 UTC
Fixed @40513:
Add member/group to role form now filters out the current role and any
of its supergroups.

Comment 6 David Lawrence 2006-07-18 02:39:59 UTC
QA_READY has been deprecated in favor of ON_QA. Please use ON_QA in the future.
Moving to ON_QA.

Note You need to log in before you can comment on or make changes to this bug.