Relative to SW2013

So the first problem with intersect I found was you can't use it in assembly only in part.

Now I have been seeing another problem. I thought first time I saw it perhaps it was just one of those things and probably wouldn't happen again.

But I have seen it several times now with no association with the other models/project it happened on.

It's seems where using intersect feature in a multibody file and then after using fillets or chamfer they can lose there association and you have to re-pick (probably applies to other features too but it's a simple example). This seems to be triggered by a full rebuild of the model in question, maybe delete a feature which can be further down the tree and have zero impact on the previous intersect feature/fillet command much high up in the history tree.

Has anyone else noticed this? Came off support recently so can't check if it has been raised as a problem.