Bug 1534858 - [trello sg1xw7gG] Cannot set preferred landing page normally when user have multiple projects
Summary: [trello sg1xw7gG] Cannot set preferred landing page normally when user have ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.9.0
Assignee: David Taylor
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-16 06:08 UTC by shahan
Modified: 2018-03-27 09:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-01-24 15:55:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.9 RPM Release Advisory 2018-03-28 18:06:38 UTC

Description shahan 2018-01-16 06:08:59 UTC 
Description of problem:
 Cannot set  preferred landing page normally when user has multiple projects

Version-Release number of selected component (if applicable):
 v3.9.0-0.19.0

How reproducible:
Always

Steps to Reproduce:
1. create two projects with user
2. Login web console and click user account on the top-right of console
3. select 'Set Home Page' in the drop-down list
4. try set preferred landing page

Actual results:
 The Save button always be disabled no matter what user select.

Expected results:
Should set preferred landing page successfully.

Additional info:
Comment 1 Samuel Padgett 2018-01-16 16:51:00 UTC 
https://github.com/openshift/origin-web-console/pull/2669
Comment 2 David Taylor 2018-01-16 18:01:03 UTC 
Merge PR:  https://github.com/openshift/origin-web-console/pull/2669
Comment 3 Yanping Zhang 2018-01-22 07:51:11 UTC 
Tested against OCP v3.9.0-0.22.0, the issue has been fixed. pls move to ON_QA, thx!
Note You need to log in before you can comment on or make changes to this bug.