Bug 1392266

Summary: Red Hat Mobile Application Platform 4 - New Project wizard page should have the "Next" button disabled
Product: Red Hat xPaaS Reporter: hchin
Component: DocumentationAssignee: Vikram Goyal <vigoyal>
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecified   
Target Milestone: ---   
Target Release: ---   
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: 2017-03-08 03:43:01 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:
Attachments:
Description Flags
The name field of the project is a mandatory field, the "Next" button should stay disabled until this field in populated none

Description hchin 2016-11-07 03:55:43 UTC
Created attachment 1217852 [details]
The name field of the project is a mandatory field, the "Next" button should stay disabled until this field in populated

Description of problem: New Project Wizard


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


How reproducible: Creating a new project, without providing a name


Steps to Reproduce:
1. Go to "Projects" tab on the "Red Hat MAP App Studio"
2. Click on "New Project" button
3. Select "AngularJS Hello World Project" template
4. Do Not Provide a Name for the project.
5. Scroll down to the "Next" button, notice that it is NOT DISABLED.
6. Possible to click the "Next" button.
7. The project build hangs, with a moving progress-bar....and does not complete, ever.

Actual results:
After clicking the "Next" button, the project build hangs, with a moving progress-bar....and does not complete, ever.

Expected results:
The "Next" button should be DISABLED. This button stays disabled until Project Name is provided.

Additional info:

Comment 1 Vikram Goyal 2017-03-08 03:43:01 UTC
Hi there,

This doesn't seem to be a bug with the xPaaS Docs. If I am missing something and if you can provide more content, please reopen.