Blocking change sets at the "destination" project as opposed to "source" project area.
We have a project area which contains work items we don't want people to associate change sets with.
The solution is to use the "restrict change sets" functionality in the "source" project area which contains the code.
i.e., in the "source" project area, use: Team Config > Operation Behavior > Source Control > Save Change Set Links and Comments > Restrict associating change sets with work items in the same project area as the component owner.
But the challenge is that we have 30 project areas with streams containing code, and we had to make this change in 30 different places.
Is there a way to put this at the "destination" project area and say that no one should be able to commit code against its work items? Or is this an enhancement request that no one has yet thought of?
The solution is to use the "restrict change sets" functionality in the "source" project area which contains the code.
i.e., in the "source" project area, use: Team Config > Operation Behavior > Source Control > Save Change Set Links and Comments > Restrict associating change sets with work items in the same project area as the component owner.
But the challenge is that we have 30 project areas with streams containing code, and we had to make this change in 30 different places.
Is there a way to put this at the "destination" project area and say that no one should be able to commit code against its work items? Or is this an enhancement request that no one has yet thought of?