1

On my hosted instance, for this particular Case.

https://bhwh.fogbugz.com/default.asp?133#736

I tried several times adding time for today 1/3/2011 from 1:15 pm - 1:30 pm. Each and every time, when I clicked save, it saved the data as 1:15pm - 1:24pm. I changed the way I entered the time (was using 1.30 - and it changed it to 1:30pm, then I entered it directly as 1:30 pm), but it still changed it.

Even the elapsed time on the case showed 10 minutes.

Finally I had to adjust the hours to 1:00 pm - 1:15 pm to get it to work properly.

flag

3 Answers

1

What time was it?
I'm guessing it was about 1:24, give or take a few fractionals...
FB doesnt let you set timesheet entries in the future, so it automatically cuts down your timesheet entry to the current time. There is no override, AFAIK.

link|flag
We've discussed letting people put intervals like 10 minutes into the future, so that you can end your interval at 1:24, but mark it ended at 1:30 for the sake of round numbers. – Rich Armstrong Feb 1 2011 at 15:47
0

Can't say for sure, but I'm guessing there is time overlap for the particular user. Is there already an entry starting from 1:24pm for the user?

link|flag
0

If you didn't have a conflicting interval, this might've been something to do with the server time. We've seen instances of this, where the Javascript of the interval editor is pulling a server time that's not visible anywhere else on the server. If this persists for you and you can't find an incorrect time on the server, please contact us.

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.