Bug 1188072 - Edit role lists itself as a "member of" option, causes exception if selected
Summary: Edit role lists itself as a "member of" option, causes exception if selected
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Zanata
Classification: Retired
Component: Component-UI
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Alex Eng
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-02 00:22 UTC by Damian Jansen
Modified: 2015-06-04 02:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-06-04 02:36:30 UTC
Embargoed:


Attachments (Terms of Use)
Stack (23.89 KB, text/plain)
2015-02-02 00:22 UTC, Damian Jansen
no flags Details

Description Damian Jansen 2015-02-02 00:22:23 UTC
Created attachment 986899 [details]
Stack

Description of problem:
Editing of a role in Administration shows a list of roles to set this as a member of, including the one being editing. Selecting the role and pressing Save causes a org.jboss.seam.security.management.NoSuchRoleException

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

How reproducible:
Easy always

Steps to Reproduce:
1. Log in as admin, go to Administration -> Manage Roles
2. Create a role: click New role under menu, enter name, press save
3. Click the same role, to edit it
- note that the role name shows in the list, under Member of
4. Click the checkbox for the Member Of option for this role
5. Press Save

Actual results:
NoSuchRoleException

Expected results:
This role should not be listed in the roles it can be a member of.

Additional info:
Exception text attached

Comment 1 Alex Eng 2015-02-05 00:17:53 UTC
Damian, 

Can you check if this issue still occurring after admin page changes?

Comment 2 Damian Jansen 2015-06-04 02:36:30 UTC
Tested at 5578463242d554d4d0a3a88c96efcbb9987dbc69, works fine


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