Bug 1028061 - User creation: should not be prompted to select default environment.
User creation: should not be prompted to select default environment.
Product: Red Hat Satellite 6
Classification: Red Hat
Component: WebUI (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified (vote)
: Unspecified
: --
Assigned To: Eric Helms
Katello QA List
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2013-11-07 10:11 EST by Corey Welton
Modified: 2014-03-11 12:43 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-03-11 12:43:48 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Corey Welton 2013-11-07 10:11:26 EST
Description of problem:
Per bug# 1011528, we now no longer allow selection of environment in user defaults.  However, this can still be selected/setup at user creation.  It doesn't make sense to allow that in user creation when it can't be changed later, particularly when this workflow is no longer supported.

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

How reproducible:

Steps to Reproduce:
1. Administer > Users > +New User
2. Fill in info; select a default org
3. Observe resulting option to select environment.

Actual results:
Per aformentioned bug, assigning a user to an environment is no longer supported. 

Expected results:
We should no longer be offering the option to select an environment.

Additional info:

There's probably something that needs to be done for the CLI as well?
Comment 1 RHEL Product and Program Management 2013-11-07 10:26:46 EST
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Bryan Kearney 2014-03-11 12:43:48 EDT
Closing old bugs which are not relevant based on new UI and CLI

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