Quantity values should be shown as entered, unless arithmetics was used that makes rounding necessary to remove spurious digits introduced by conversion factors.
|· · ·|
|Open||None||T56318 Quantity datatype (tracking)|
|Resolved||thiemowmde||T95425 [Bug] Quantity formatter rounding causes significant data loss|
|Invalid||None||T117457 Do not apply rounding when formatting Quantities (unless unit conversion was applied)|
|· · ·|
Bumping this to UN priority, because it causes data loss. Unless I'm very confused, we can easily do this NOW, without the full solution discussed in T105623: [Task] Investigate quantification of quantity precision (+/- 1 or +/- 0.5). All that needs to be done is to disable rounding when calling the plain text formatter for filling the text field for editing.
Why did this drop off so many sprints? Is there a hidden blocker or complication?
Reverting myself wrt "unbreak now". Seems I got myself confused. There is no data loss issue. We do not apply rounding for the plain text value we fill into the text box for editing.
This should still be done with high prio. The change is really trivial. Just don't apply rounding for now, until we have unit conversion.