Question

What I want to be able to do is to setup my working schedule like this:

• 10% Project A
• 10% Project B
• 80% unallocated

and have some option to tell FogBugz that I am allocating at least 10% of my time to Project A, not exactly 10% of my time.

My situation: I currently have two projects that I am assigned to. Generally I spend most of my time working on whichever project has the earliest next milestone deadline, but I do regularly spend at least a little time with the other project as well. So if the next milestone deadline is in Project A, I want the 10% allocation for B to be protected, but the allocation for A should be effectively 90% (10% protected + 80% unallocated).

Case FC1874388

Answer 1

Got it. I have opened a feature request. If you would like to see this feature implemented, please up-vote this question.

Thanks! It seems like we would want to keep the "exactly" option around, to best handle a side project (where the next milestone in that project might be before the next milestone in your main project). It sounds like a dropdown in the per-project percent times table where you could specify 'exactly 10%' or 'at least 10%' would do the trick?

Answer 2

I'm almost positive "at minimum" is how it works already based on the test below. I actually want it to be "exactly" instead of "at minimum", since it makes my FB schedules relatively inaccurate.

Here's my "test" setup:

• Project A - has one case estimated at 100 hours assigned to me, 1% Time Allocation
• 99 % - Other FogBugz tasks

When I run the per-user Burndown chart in this configuration (for a project other than A), the schedule slips by several months relative to there being no 100-hour case. Even though the 100-hour case project has a time allocation of 1%--apparently FogBugz thinks I'm working on it.