Bug 1025148 - Change "Entry Type" shouldn't impact VMM's behavior
Summary: Change "Entry Type" shouldn't impact VMM's behavior
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Certification Program
Classification: Red Hat
Component: Certification Workflow Engine
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Kun Yan
QA Contact: Suprith Gangawar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-31 06:10 UTC by Huan Zhang
Modified: 2015-12-23 10:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-23 10:40:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1024585 0 unspecified CLOSED Original make selection is invalidated when re-select the Entry type 2021-02-22 00:41:40 UTC

Internal Links: 1024585

Description Huan Zhang 2013-10-31 06:10:13 UTC
This is fine with Firefox, but when using Chrome:

1) go to the "Create New Entry" page
2) leave the "Entry Type" as "Create Both"
3) select/input VMM info
4) change the "Entry Type" to other value

The value of Make looks not changed, but actually, the value couldn't be passed to the backend; Clicking the CONTINUE button, an alter info will popup and says "Please select make".

The action of changing "Entry Type" shouldn't impact the VMM's behavior.

Comment 1 Huan Zhang 2013-10-31 06:12:46 UTC
Let's delay this to 5.3 release, as this is really a little tricky.


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