Estimated Time value is corrupted
Estimated Time value is corrupted.
Steps to reproduce:
1. Open an issue.
2. Set Estimated Time to '999999999999999999999999999999'.
Estimated Time is equal to '999999999999999999999999999999'
#1 Updated by Jean-Philippe Lang almost 7 years ago
- Status changed from New to Confirmed
Yes, this happends when we exceed the floating-point precision:
irb(main):001:0> "%02f" % 999999999999999999999999999999.0 => "1000000000000000019884624838656.000000"
A solution would be to validate the estimated time against a reasonable range of values (eg. 0 - 1000000), what do you think?
#2 Updated by Daniel Felix over 6 years ago
I give some other solution on #12955.
What do you think about changing the datatype from float to decimal, which is much more accurate? We're using decimal in all of hour analytics, because it behaves greater on converting, has a better support for such big numbers without falling back to exponentials and is supported in all databases too.
This would solve this problem without the limitation of the estimated time to some value like 1.000.000.