-
Bug
-
Resolution: Fixed
-
Low
-
10.2.1, 5.12.15, 5.17.4, 10.3.3
-
2
-
Severity 3 - Minor
-
8
-
Issue Summary
When using Jira with German locale, the behavior for editing float values is not consistent.
Steps to Reproduce
- Set up a Jira environment with German locale.
- Create a test object schema.
- For any object, create an attribute of type float.
- When adding or editing a value for a float attribute in the Object Schema view, if you add the number using a comma (the standard for German locale), the error message "Value is not valid (Float)" will be shown. The error does not happen if a dot is used instead of a comma, but the value will be displayed correctly with the comma.
- When adding or editing a value for the same attribute in the Object view, however, it is possible to do so using a comma OR a dot. However, the value is then displayed with a dot.
Expected Results
Assets should fully respect the German locale settings and allow editing of float attributes with a comma. The values should also be consistently displayed with a comma.
Actual Results
- When adding or editing a value for a float attribute in the Object Schema view, if you add the number using a comma (the standard for German locale), the error message "Value is not valid (Float)" will be shown. The error does not happen if a dot is used instead of a comma, but the value will be displayed correctly with the comma.
- When adding or editing a value for the same attribute in the Object view, however, it is possible to do so using a comma OR a dot. However, the value is then displayed with a dot.
Workaround
Versions Tested
Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below:
Testing Requirements | Version | Affected Version |
---|---|---|
Customers Reported Version | 5.17.4 | Yes |
Most Recent Bug-Fix Release | 10.2.1 | Yes |
Previous Major Release | ||
Most Recent LTS | 5.12.15 | Yes |
Previous Supported LTS | ||
Other Versions.. | ||
(Add rows as needed) |
- causes
-
JSDSERVER-16134 Decimal separator is removed when saving float values in Assets objects
-
- Closed
-
- relates to
-
JSDSERVER-16277 Inconsistent locale behaviour for decimal separator in Assets
-
- Gathering Impact
-
- links to
floated value is consistent.