Loading Profile...
Twitter,
Facebook, or email.
Hey there, we found a small bug in the web client - when you go into 'hours remaining' when editing a task, and the digit 0 is the only thing you type, even if it's overwriting the "2" in "32", and then tab out, it'll mark the task as done when it shouldn't. Thanks in advance for fixing this little bug. ;)
- Jeanie
I’m
bugged. heh heh
typing 0 in web client 'hours remaining' always changes task to done
-
Hi Jeanie,
Thanks for this report, I just verified it on my system. It definitely should not be doing that. I will let the team know about this one momentarily.Comment -
-
I’m
thankful! :D
thanks a bunch, and thanks for your prompt reply! :D -
-
Not a problem. Just an update too, the team is actually working on it right now (or at least the ones that haven't already gone home, Fridays! sheesh). Sounds like it will be fixed in the next release.
-
-
I’m
confused
In the web client, if you set the "Hours remaining" value on a Task to "10", it seems to treat it as if you entered "0" (zero). The Task is marked as Done, and moves to the final column.
In fact, if you enter any value which includes a zero, it is treated as if it was the number zero - "04", "40", "400" all do this.
This is happening in ScrumWorks Pro, Version: 4.3.0, Build: 2010-01-28 12:18 r25120
A fix would be appreciated ;-)
Mike Brown
ProQuest
This reply was created from a merged topic originally titled
Task hours remaining interpreting zeroes wrongly. -
-
Hi Mike,
We're aware of this issue and a fix is in progress. It will be available in the 4.4 release of ScrumWorks at the end of Q2. -
-
Hi Mike,
This is now fixed as of Release 4.4. -
EMPLOYEE
EMPLOYEE
