Actions
Bug #17325
closed
We can't choose between string and json for global parameters
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
For node properties, we have a choice between json and string value, and when we choose json, it checks json validity.
We need the same choice and check for global parameter.
(it's only an UI problem, backend support both, but currently if the json is incorrect, it is taken as a string, which is unlikely what the user wants)
Updated by 
Updated by 
Updated by 
Updated by
Actions