Bug 1371207

Summary:	Chargeback assignments are not saved when Rate is <Nothing>
Product:	Red Hat CloudForms Management Engine	Reporter:	Matouš Mojžíš <mmojzis>
Component:	UI - OPS	Assignee:	Brian McLaughlin <bmclaugh>
Status:	CLOSED WONTFIX	QA Contact:	Parthvi Vala <pvala>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.6.0	CC:	hkataria, jhardy, mpovolny, obarenbo
Target Milestone:	GA
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ui:chargeback
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-20 11:54:37 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:

Description Matouš Mojžíš 2016-08-29 14:50:17 UTC

Description of problem:
Issue on upstream master: https://github.com/ManageIQ/manageiq/issues/10596

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

How reproducible:
Always

Steps to Reproduce:
1. Cloud Intel -> Chargeback -> Assignments
2. Select Compute or Storage and Assign to for example Enterprise or Tenants.
3. Save button is not disabled anymore, but when I save it it resets Assign to default().

Actual results:
I have to select rate to make it really saved.

Expected results:
Either button should be disabled or it should be saved even when rate is not set.

Additional info:

Comment 2 Harpreet Kataria 2016-08-29 19:19:08 UTC

Brian,

Can you take a look, maybe Flash message is not getting rendered for required fields, or see if there are any errors in log. Let me know if you need help.

Thanks,
~Harpreet

Comment 3 Josh Carter 2018-09-20 11:54:37 UTC

Bug Closure

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!