Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.5.2
-
Fix Version/s: None
-
Component/s: Client Interface
-
Labels:None
Description
I'm not sure whether this is a bug or not.
This issue affects the client interface during upgrades where the following conditions are met:
1. The config option is addable by clients, but not editable
2. The config option already exists on the service in question
3. The client goes to update the service and chooses a different pricing (i.e. package or term)
4. The existing config option (i.e. #1 and #2) is available to the new pricing.
Then, the existing config option does not appear in the form to be added. It is not editable, so it does not appear in the form, but it is removed from the service because the pricing has changed. Any new pricing requires new config options be set, but the existing option is not available to be added as a new option because it currently exists.
