You can represent a task beginning, then getting interrupted, and then
restarting by using the split task tool on the toolbar. Unfortunately the
dates you gave for your example doesn't really fit into that approach
because there's no gap of non-working time between the end of the first
segment and the beginning of the second. Tasks have a concrete duration and
a specific and observable scheduled start and finish. Your "objective" and
"threshold" don't seem to be that sort of things but more accurately
represent deadlines or reporting intervals. It sounds like you're saying
that Project X (with an undefined start and duration) should take place
sometime during the 1st Qtr of 06 but must be completed by the end of the
2nd Qtr. That is well and good, but those "windows" are NOT what a project
plan is referring when it lists the task start and end dates. A project
plan doesn't say "We want this to happen during Q1-06." A project plan says
"We *will* start on 15 Oct 05 and will direct our resources to show up on
that date prepared to do the following specific physical activity. If all
goes according to plan we calculate that we will finish on 20 Jan 06. Our
deadline by which we must finish in order to meet our contracts is 31 Mar
06." It is an action plan, something that if followed by our resources
step-by-step will result in the successful accomplish of the project's
objectives, much more concrete than merely a list of the desired time
periods during which we want Project X will take place.
Just some ideas to think about that might help ...
