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 just mentioned the time tracking page for comparison. Thanks for testing, it looks like the CultureInvariantValues property doesn't affect the values entered , just the min, max and compare values on the validator. > The CultureInvariantValues property does not affect values that are entered by users of the control on a Web page. If you can try the first option , using the current culture and changing the validation culture on the properties that would probably work better.
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 just mentioned the time tracking page for comparison. Thanks for testing, it looks like the CultureInvariantValues property doesn't affect the values entered , just the min, max and compare values on the validator. > The CultureInvariantValues property does not affect values that are entered by users of the control on a Web page. If you can try the first option , using the current culture and changing the validation culture on the properties that would probably work better.