Re: HOWTO have tasks without wbs code by davegb
davegb
Thu Sep 14 17:25:29 CDT 2006
Andr=E9 wrote:
> Hi,
> Thanks for your advice.
> Just to clarify, I really meant WBS and not ID codes.
> You are right, WBS codes are optional therefore I can delete them at my
> will.
> My "problem" now is that when I do Project->WBS->renumber, my phony
> tasks get numbered. My workaround for the moment is to move them
> temporarily to the end and delete the generated WBS codes before moving
> them again to the top.
>
That would be easy to do with a simple macro. Set a boolean field to
mark those "dummy" tasks, then have the macro delete the WBS code for
those marked tasks.
> Thanks,
> Andr=E9
>
> davegb wrote:
> > Andr=E9 wrote:
> > > Hi all,
> > >
> > > I have a schedule where in the top lines I keep the contract award and
> > > program milestones with deadlines dates. These tasks are linked (with
> > > SS relationships) to the corresponding review activity in the network
> > > schedule. This way I can see if I have a problem in meeting customer
> > > predefined dates for the milestones without setting constraint dates
> > > (that could spoil the Critical Path).
> > >
> > > My question is how can I exclude these tasks from having a WBS code?
> > >
> > > I saw a schedule like this in the afmc pamphlet 63-5.
> > >
> > > Thanks you all,
> > > Andr=E9
> >
> > I'm not clear on what you're asking, Andre. Seems to me you just don't
> > give them a WBS code. It's an optional field.
> >
> > If you're referring to an ID number, you can't have tasks without ID
> > numbers. Project abhors blank lines in the middle of a task list and
> > will punish you without mercy until you remove them! I notice 63-5 has
> > blank lines, but they do have ID numbers, which means project thinks
> > they are tasks. Not a good practice, in my opinion. Others may
> > disagree.=20
> >=20
> > Hope this helps in your world.