A task is action that produces a single deliverable, not just the name
of an activity. Is that what each of these tasks do or are they
really series of separate tasks? For example, let's say your
department will be sending out a short newsletter once a month for the
next year and you're tasked with editing it, a job that will take 2
days per month. That's not as single task "edit newletter" lasting a
year requiring a couple of days attention each month but really it's a
series of 12 separate and distinct tasks - "edit January newletter,"
"edit February newsletter," "edit March newsletter" and so on and the
project file should list them as such. "Edit Newletters" would become
a summary task with the individual months shown as 12 2-day duration
tasks indented under it. You could enter such manually with SNET
constraints to push each subtask into its proper month or you could
use arecurring task to automatically schedule this sort of thing.
If the tasks you ask about in your post are truly producing just a
single deliverable each, why are you setting them to a years duration?
A task that will require me to put in 2 hours of work and is due the
end of June is not a 1 month duration task, it is a 2 hour duration
task with a deadline date of July 1st. If your task requires, say,
24 days of work to complete and could start Monday, even though it's
not due for a year, why put it off? Why not just do it all at once,
put the deliverable it produces on the shelf until it's needed, and
move on to something else? If there's a reason you CAN'T do it like
that, if it truly must be be split up into 2 days per month segments
extending for the next year, I'd be very suspicious that what you're
describing as a single task is not really multiple tasks as discussed
above and you really should revisit your task breakdown and make it
more detailed.
Steve House