Some locales use point symbol to delimit decimal parts of a number and other use comma.
We would love to see both accepted when entering numbers. Currently when we create a new issue with a wrong decimal separator, no error is shown - the issue is saved without estimation and the issue creator can easily miss the problem. That is really inconvenient and leads to problems in the business process.
In short, 0.25 and 0,25 should both be accepted in the estimation field.
Comments: Here is a result of my testing. I changed my locale to Netherlands, Dutch. * entered 5.5 which saved and displays as 55,00 as expected * entered 5,25 which saved and displays as 5,25 as expected * entered sss which the validator fired as invalid input So right now I don't see any issue, and it wouldn't be possible to handle both localization formats at the same time because the decimal and comma are used in different ways as shown in my tests.
We would love to see both accepted when entering numbers. Currently when we create a new issue with a wrong decimal separator, no error is shown - the issue is saved without estimation and the issue creator can easily miss the problem. That is really inconvenient and leads to problems in the business process.
In short, 0.25 and 0,25 should both be accepted in the estimation field.
Comments: Here is a result of my testing. I changed my locale to Netherlands, Dutch. * entered 5.5 which saved and displays as 55,00 as expected * entered 5,25 which saved and displays as 5,25 as expected * entered sss which the validator fired as invalid input So right now I don't see any issue, and it wouldn't be possible to handle both localization formats at the same time because the decimal and comma are used in different ways as shown in my tests.
