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: I have tried the CultureInvariantValues on the IssueDetails page. The locale is set Russian, so the decimal delimiter is comma ',' 1. When I enter '1,1' into the estimation field - it is saved properly 2. 'sss' - renders a "not a number" error 3. '1.1' - does not display an error and clears the field contents on save. I would not normally expect that. It should either be parsed and saved or I should get the error message
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: I have tried the CultureInvariantValues on the IssueDetails page. The locale is set Russian, so the decimal delimiter is comma ',' 1. When I enter '1,1' into the estimation field - it is saved properly 2. 'sss' - renders a "not a number" error 3. '1.1' - does not display an error and clears the field contents on save. I would not normally expect that. It should either be parsed and saved or I should get the error message