I have a complex plan and am looking to extract some sections of it into sub plans. I don't like links between plans (preferring to manually control these using named dependencies). Before I just rip out a section of the plan I prefer to check to see what relationships the rest of the plan have on this section.

To do this I have designed a simple highlight filter that is meant to highlight tasks that have a dependency on a defined section of the plan. The filter is:

Predecessors - is less than or equal to - "less than:"? (enter 12)

AND Predecessors - is greater than or equal to - "greater than:"? (enter 9)

This seems to work most of the time however a task that has the predecessor 10,2 doesn't trigger the highlight. Changing it to 10 does trigger and then when I change it back to 10,2 it stays triggered! Note that I am re-applying the filter with each change.



I am not used to MSP being inconsistent in this way, I would have expected the 10,2 to trigger in the first place OR not trigger the second time.

Note that most tasks have multiple dependencies and this doesn't appear to impact the filter.

Does anyone know what is going on here? Do you have any tricks or techniques to identify the impact of a section of the plan before removing it?

TIA