G
Guest
It sounds to me like it is working as designed. She first
told it that she worked more than planned so it resets
assigned work to 8. Then she tells it she only worked 7.
I don't think this sounds like a bug. This is how the
timesheet works and should work. In the same respect if
she left it alone and logged 6 hours the remaining would
show 1. It is calculating properly.
Before saving or updating, they changes the value to a
smaller number. PWA sets the Remaining work to the
difference between the large number originally entered
and the current number.
timesheet. Remaining Work is set to 0. She realizes the
actual value should be 7, so changes the 8 to 7.
Remaining Work is automatically set to 1. Susan has not
saved or updated her data at all yet. PWA forgets the
original Remaining Work that was on the timesheet before
edits were done.
remaining work to 0, the republish that task.
told it that she worked more than planned so it resets
assigned work to 8. Then she tells it she only worked 7.
I don't think this sounds like a bug. This is how the
timesheet works and should work. In the same respect if
she left it alone and logged 6 hours the remaining would
show 1. It is calculating properly.
Timesheet, and wonder if anyone has a solution.
view that is larger than the current Remaining Work.
Before saving or updating, they changes the value to a
smaller number. PWA sets the Remaining work to the
difference between the large number originally entered
and the current number.
assigned to Susan. Susan enters 8 hours on her
timesheet. Remaining Work is set to 0. She realizes the
actual value should be 7, so changes the 8 to 7.
Remaining Work is automatically set to 1. Susan has not
saved or updated her data at all yet. PWA forgets the
original Remaining Work that was on the timesheet before
edits were done.
have to manually go into the project file and change the
remaining work to 0, the republish that task.
is it a bug / undocumented feature?