Bug 1111649 - UI popup "email can't be blank" while assigning role to a user that was created earlier without email-id
Summary: UI popup "email can't be blank" while assigning role to a user that was creat...
Keywords:
Status: CLOSED DUPLICATE of bug 1099988
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Users & Roles
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Dominic Cleal
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-20 16:00 UTC by Sachin Ghai
Modified: 2014-07-01 14:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-24 15:36:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
validation of email address while assigning role to user. (36.82 KB, image/png)
2014-06-20 16:00 UTC, Sachin Ghai
no flags Details

Description Sachin Ghai 2014-06-20 16:00:20 UTC
Created attachment 910812 [details]
validation of email address while assigning role to user.

Description of problem:
I created a user and without email-id. User was created successfully. Later I created a new role. But when I assigned the role to created user, the create user form pops-up with validation error along with "Email Address" text box 

"can't be blank"

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

How reproducible:
always

Steps to Reproduce:
1. create a user without email id
2. create a role
3. assign role to user by editing user. 


Actual results:
validation error raised on UI while assigning role to user that email address can't be blank

Expected results:
No such error should be raised while assigning role to user instead if email-id is required then it should be validated while user creation only

Additional info:

Comment 2 Dominic Cleal 2014-06-24 15:36:04 UTC

*** This bug has been marked as a duplicate of bug 1099988 ***


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