It's all about the answers!

Ask a question

Prevent sharing specific components

Muhammad Moid (141634) | asked Oct 26 '15, 2:45 a.m.
edited Oct 26 '15, 2:45 a.m.

I want to prevent specific components to be shared with other teams in two cases.

1. Prevent component sharing from repository work space to Stream
2. Prevent component sharing from local sandbox to repository work space ( sine in some cases people works collaboratively using their repository  work spaces)

Muhammad Moid

One answer

permanent link
Geoffrey Clemm (30.1k33035) | answered Oct 26 '15, 5:47 p.m.
(1) Whether or not someone can add a new component to a stream is controlled by the "Add components to a stream" permission on that stream.
(2) You cannot "share" a component from a local sandbox to a repository workspace ... you have to create the component on the stream before you can share content from the local sandbox to the workspace.   But also note that you should never try to work collaboratively by sharing a single repository workspace with multiple sandboxes ... a given repository workspace should only be associated with a single sandbox ... you can reassociate a repository workspace with a new sandbox, but then it should no longer be used with the original sandbox (except for a few unlikely edge cases).

Muhammad Moid commented Oct 27 '15, 3:03 a.m.

Got your point#2.

Regarding point#1, Let me give you a scenario for it.

I have one Stream (contain 2 components i.e. component1 & component2) and two Developers (i.e. DevA and DevB) sharing their work on that stream.

DevA is working component1, component2 and on a new component i.e. component3, DevA do not want component3 to be shared on the Stream while delivering all his work. The objective is that DevA do not want to share component3 with his team members for the time being.

Geoffrey Clemm commented Oct 27 '15, 7:23 p.m.

Yes, there are many good reasons for restricting who can add a component to a stream.  In the case you describe, you could remove component add permission from all developers (to avoid mistaken addition of components to the team stream), and then only give developers component-add permission for enough time for them to add a component when it is time for it to be added.

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.