Question

We work on multiple website build projects for clients at once, so can typically work on a dozen cases or more in a day (although other days, just one or two) - some bugs, others 'new build' tasks.

Our billing team would like to see timesheet entries for each day/week/month totalling the entire work day/week/month (8/40/? hours).

I think that means we need to use Schedule Items to record time spent in meetings/etc in order to log all possible time, rather than simply setting the "% time spent on FogBugz tasks" to something less than 100% (and assuming the rest is non-task time).

I don't think that's right, and don't understand enough about EBS yet to know what the effects of that might be. Is their idea sufficiently bad to cause us problems later, or should we run with it?

Phil

Answer 1

I would run with it. It ought to work, the only issue would be that it might foul up your estimate history graph (if these schedule items are not truly being estimated before they are performed), but you could fix that manually if you wanted by discarding the schedule items from the estimate history. You could even write a plugin to do this automatically if you knew that you didn't want to include the schedule items.