In GP v3.2, this does not happen.
In GP v3.1, dragging tasks with resoruces onto a new level in the hierarchy, does break the assignment of resources and the tasks loose costs.
Is there a way to fix this in GP v3.1, or expectations to fix?
In GP v3.2, this does not happen.
In GP v3.1, dragging tasks with resoruces onto a new level in the hierarchy, does break the assignment of resources and the tasks loose costs.
Is there a way to fix this in GP v3.1, or expectations to fix?
We do not provide updates to the older versions, sorry.