Bug 850703 - 'Read Right' checkbox is not behaving as expected
'Read Right' checkbox is not behaving as expected
Status: NEW
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Site Publisher (Show other bugs)
5.2.1.SP.GA
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Default User
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-22 03:43 EDT by bkramer
Modified: 2012-08-22 04:01 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description bkramer 2012-08-22 03:43:37 EDT
Description of problem:
Under Permissions Tab,
Edit any user permissions, uncheck 'Read Right' checkbox and click on save button
'Read Right' option is still appearing as 'true'.

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

How reproducible:
Always

Steps to Reproduce:
1) Log into Site Publisher as root;
2) From the menu navigate to Group -> Administration -> Manage Categories;
3) From the list of Categories -> acme -> in the Action select "Edit Category Tree";
4) Click on "+" to list categories;
5) From the right table -> for one category name -> select "Permission Management" icon;
6) Select user by clicking on pencil icon in Action column. This will display selected user in the "Add permission to that node" section with all permissions.
7) Remove "Read" right by unselecting "Read" check box and click on "Save" button to save the change;
8) Select the same user again and check it's permissions and it will show again "Read" as enabled.

  
Actual results:
The checkbox appears as "checked".

Expected results:
It should appear as 'False' after uncheck the checkbox.

Additional info:

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