Bug 1732378

Summary: Defaults Application Name option to Create New Application when user doesn't have any apps
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Dev ConsoleAssignee: cvogt
Status: CLOSED ERRATA QA Contact: Ruchir Garg <rgarg>
Severity: low Docs Contact:
Priority: medium    
Version: 4.2.0CC: aos-bugs, jokerman, mmccomas, nmukherj, yapei
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:30:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yadan Pei 2019-07-23 09:17:24 UTC
Description of problem:
When user doesn't have any apps, Application Name can be only set as `Create New Applicaiton` , so it would be better if it can be selected by default

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-07-23-002801

How reproducible:
Always

Steps to Reproduce:
1. User has a project but without any apps
2. User goes to Developer Console -> Click `+ Add` -> Browse Catalog -> Choose one image from `Source-to-Image`, such as PHP -> Create Application -> Click `Try Sample`, this will fill up all necessary fields 


Actual results:
1. Create button is always disabled because Application Name dropdown still need to be selected

Expected results:
1. `Create New Application` is the only option when user doesn't have any apps, so it would be better if `Create New Application` is selected by default since user don't have any other options for Application Name

Additional info:

Comment 3 Yadan Pei 2019-09-11 07:57:21 UTC
Now the Application source defaults to 'Create Application' when user doesn't have any existing apps. Click 'Try Sample' also fills the 'Application Name' with given name


Verified on 4.2.0-0.nightly-2019-09-10-181551

Comment 4 errata-xmlrpc 2019-10-16 06:30:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2922