Bug 1439942

Summary: Service :dialog: Text box element with Integer Type shows default value '0' without even assigning one
Product: Red Hat CloudForms Management Engine Reporter: Shveta <sshveta>
Component: AutomateAssignee: eclarizi
Status: CLOSED WONTFIX QA Contact: Shveta <sshveta>
Severity: low Docs Contact:
Priority: medium    
Version: 5.7.0CC: gmccullo, hkataria, jhardy, mkanoor, mpovolny, obarenbo, tfitzger
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: service:dialog
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-02 14:30:52 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:
Attachments:
Description Flags
screenshot1
none
screenshot2 none

Description Shveta 2017-04-06 22:50:55 UTC
Created attachment 1269494 [details]
screenshot1

Description of problem:


Version-Release number of selected component (if applicable):
5.7.2.0.20170321181409_349f1b1 

How reproducible:


Steps to Reproduce:
1. Create a dialog with Text Box element .(screenshot 1)
2. Select Value Type "Integer" . Do not assign any default value
3. Use this dialog in a catalog item. Order catalog item.
text box shows default value = 0 (screenshot 2) 

Actual results:


Expected results:


Additional info:

Comment 2 Shveta 2017-04-06 22:51:21 UTC
Created attachment 1269495 [details]
screenshot2

Comment 3 Greg McCullough 2017-04-18 21:14:04 UTC
Looked into this issue a little more:

OpsUI translates the empty value to 0 ("".to_i or nil.to_i both do this)
SUI leaves the value blank.

In both UIs the value is really empty and the required flag would cause field validation to raise an error when submitting the dialog.

Makes sense to keep a blank value when no default is given so the "Required" flag works as expected.

Comment 4 Josh Carter 2018-10-02 14:30:52 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 5 Josh Carter 2018-10-02 14:33:19 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!