Bug with Autolink in MSP 2003 standard SP2

[Tomhad]

Autolink auto link auto link not working can some one actually at Micrososft
answer this question please ??

The software Microsft project 2003 standard is NOT working as described in
the manual and marketing material.

I am just about to take this to our consumer trbunal in Australia the
product as sold is not fit for purpose, this is illegal in Australia


I really need some help with this. I have been using MSProject since before
Windows and recently upgraded to 2003 Standard.

Firstly, I discovered by accident that the outlining function on the as
shipped version was not working properly and updated to SP2. (is this the
latest ???)

Now however, I am experiencing another major issue

After setting up a list of tasks with dependencise and then trying to
outline using keyboard short cuts or the mouse. MSP IS BREAKING LINKS ! even
though I have Autolink switched on

This is a real problem , thankfully it was not a big schedule but it
resulted in almost all of my links being lost or out of order !

It can be replicated by doing the following:-

Set up a three actvity schedule ABC etc, outline them under an "overall" task

Gantt shows three linked tasks with a summary, then try to move a task up or
down, the links are broken ???

This is definitly a bug, It does the opposite to what it says it does, it
does not keep the links it breaks them !!How do I get it fixed ? any one
know. ?

I am not interested in work arounds (even if there are any, it takes me too
much time already fixing MS's poor quality software) the software should
behave the way it says it does ? How can I report it to MS ?? any one know ?

This is a real nuisance

Please help

 

[John]

Autolink auto link auto link not working can some one actually at Micrososft
answer this question please ??

The software Microsft project 2003 standard is NOT working as described in
the manual and marketing material.

I am just about to take this to our consumer trbunal in Australia the
product as sold is not fit for purpose, this is illegal in Australia


I really need some help with this. I have been using MSProject since before
Windows and recently upgraded to 2003 Standard.

Firstly, I discovered by accident that the outlining function on the as
shipped version was not working properly and updated to SP2. (is this the
latest ???)

Now however, I am experiencing another major issue

After setting up a list of tasks with dependencise and then trying to
outline using keyboard short cuts or the mouse. MSP IS BREAKING LINKS ! even
though I have Autolink switched on

This is a real problem , thankfully it was not a big schedule but it
resulted in almost all of my links being lost or out of order !

It can be replicated by doing the following:-

Set up a three actvity schedule ABC etc, outline them under an "overall" task

Gantt shows three linked tasks with a summary, then try to move a task up or
down, the links are broken ???

This is definitly a bug, It does the opposite to what it says it does, it
does not keep the links it breaks them !!How do I get it fixed ? any one
know. ?

I am not interested in work arounds (even if there are any, it takes me too
much time already fixing MS's poor quality software) the software should
behave the way it says it does ? How can I report it to MS ?? any one know ?

This is a real nuisance

Please help

Tomhad,
First of all, I can't replicate your problem. Granted I'm using Project
2003 Pro with SP2 but I recall playing with the autolink feature under
Project 2003 Standard and having no issues.

My guess is you are using something other than a standard
finish-to-start links, and the help file clearly states that the
autolink feature "...only applies to contiguous finish-to-start task
relationships."

However, I couldn't get Project to NOT maintain links and it doesn't
seem to matter if the option is checked or not and the link type doesn't
seem to matter. There was one instance where the links were broken but
now I can't replicate that either.

Since the help file states that autolink is only valid for certain
links, if you have links other than contiguous finish-to-start and you
want to do a lot of task moving, I suggest you store the Unique ID
Predecessor field in a spare text field. That way, if your links are
broken they can be quickly restored.

Hope this helps.
John
Project MVP

 

[Rod Gill]

I have 2003 Pro SP2

Creating your three tasks linked I can drag the first or second task below
the last one and the link breaks. Since there is no following task with
Autolink On this is expected behaviour.

Personally, once I have most tasks and links in place I turn off Autolink so
that link changes are only what I want and expect.

With Autolink Off, moving any task maintains its links.

I suspect therefore that what you are seeing is intended behaviour. You
either need to save links before an editing session as John suggests or turn
Autolink off.

Where abouts in Australia are you? I'm based in New Zealand, but visit
Australia occasionally. I can provide advanced scheduling with project
training for your organisation if required.

 

[Steve House]

You need to have Autolink turned OFF. The setting is "autolink inserted or
moved tasks." IF it's turned ON and I insert task X between linked tasks A
and B, it will break the A->B link and create new ones in the pattern
A->X->B. Likewise if you have tasks linked A->B->C->D and use
click-and-drag to move D up to in between B & C, it will break the original
link pattern and create a new one A->B->D->C. Generally speaking having
software do this sort of thing automatically is a very very bad idea. Links
describe physical processes and schedule control logic, not just simple time
sequences. Project has no idea about the physical process your project
models and should leave what links are inserted and where they go completely
up to your decision - it should never take it on itself to tamper with your
choices or change them on its own. You may rearrange tasks many times for
different purposes during the course of developing the plan and if A is
linked to B it should stay that way regardless of where you move A or B with
respect to any other tasks, regardless of what order you sort them, and
regardless of whether you later insert other tasks in between them. The
direct link A->B should remain inviolate unless and until you explicitly
decide to change it. Frankly, IMHO the autolink "feature" is a bug that
should be removed completely from the product so that creating and adjusting
links would always be a manual process by necessity.

 

[Mike Glen]

You need to have Autolink turned OFF. The setting is "autolink
inserted or moved tasks." IF it's turned ON and I insert task X
between linked tasks A and B, it will break the A->B link and create
new ones in the pattern A->X->B. Likewise if you have tasks linked
A->B->C->D and use click-and-drag to move D up to in between B & C,
it will break the original link pattern and create a new one
A->B->D->C. Generally speaking having software do this sort of thing
automatically is a very very bad idea. Links describe physical
processes and schedule control logic, not just simple time sequences.
Project has no idea about the physical process your project models
and should leave what links are inserted and where they go completely
up to your decision - it should never take it on itself to tamper
with your choices or change them on its own. You may rearrange tasks
many times for different purposes during the course of developing the
plan and if A is linked to B it should stay that way regardless of
where you move A or B with respect to any other tasks, regardless of
what order you sort them, and regardless of whether you later insert
other tasks in between them. The direct link A->B should remain
inviolate unless and until you explicitly decide to change it. Frankly,
IMHO the autolink "feature" is a bug that should be removed
completely from the product so that creating and adjusting links
would always be a manual process by necessity.

 

[Mike Glen]

Hi Steve,

I agree with your sentiments absolutely, with one exception. As I
understand software, the definition of a "bug" is something that goes wrong
or doesn't work as it was designed to do, In this case, this is a design
feature that should never have been allowed. It can't be a bug as it works
as it was designed. Blame the designers for their lack of understanding of
the project management planning process. One day, they might listen to what
we've been saying for nearly a decade!

Mike Glen
Project MVP

 

[Steve House]

Yes, you are right. Rather than "bug" perhaps "nuisance feature" is a
better term.