Bug 1392266 - Red Hat Mobile Application Platform 4 - New Project wizard page should have the "Next" button disabled
Summary: Red Hat Mobile Application Platform 4 - New Project wizard page should have t...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat xPaaS
Classification: Red Hat
Component: Documentation
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vikram Goyal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-07 03:55 UTC by hchin
Modified: 2017-03-08 03:43 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-08 03:43:01 UTC
Target Upstream Version:


Attachments (Terms of Use)
The name field of the project is a mandatory field, the "Next" button should stay disabled until this field in populated (366.39 KB, image/png)
2016-11-07 03:55 UTC, hchin
no flags Details

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.


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