Can this burndown error be fixed?
Basically we had someone accidentally include some extra zeros on theirs hours on one of their tasks. This caused the burndown to go very wonky. Is there some way to fix this? Perhaps some way to remove the multi-zero state of the work item from history? I am willing to update the DW or CCM database directly if this can't be done through one of the clients. I also know how to use the API if that will help.