It's all about the answers!

Ask a question

Blocking change sets at the "destination" project as opposed to "source" project area.

Vivek Iyer (15212527) | asked Jun 12 '12, 4:49 p.m.
retagged Jun 25 '12, 11:36 a.m. by Evan Hughes (2.4k1318)
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?

One answer

permanent link
Evan Hughes (2.4k1318) | answered Jun 25 '12, 11:36 a.m.
It looks like an enhancement request that nobody has thought of. :(

In the meantime, you could inherit the the configuration from your source project areas from another project area. 

Vivek Iyer commented Jun 25 '12, 12:42 p.m.

Can Team Config be inherited?

We are on, and use process inheritance extensively. The operation behavior to restrict change sets to a project area is in the Team Config section which cannot be inherited as far as I know. Is this new in 4.0?



Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.