Closed cthompson165 closed 1 year ago
Thanks for reporting it will be fixed in an upcoming release.
Is there an update to this issue? I would like to know when this is fixed. It is causing quite a bit of frustration for our teams.
Just discovered this as well, so when we want to use the average value, we sat "4.5" but it gets saved as "4,5" which is translated as 45 in the decimal field :(
Hi! this problem depends on azure for the majority 4,5 works fine, I will try to do a workaround this week.
H! I fixed the decimal point bug, it will be released on Friday.
We use the cards that have a 0.5 option but selecting it from the "choose one to commit the value to the work item" section does nothing. Same thing with entering as a custom value. In order to set a decimal point value I have to open the backlog item/bug and manually update.
Decimal values used to work. Seems like it stopped working 3 or 4 months ago.
UPDATE - if I enter as "0.5" from the custom value it does update the item. But it updates as "0,5" on the estimate card and a 5 in the item estimate field.