Reuse the existing component in a new stream in a new project
Accepted answer
So it is one component, shared by multiple streams (each having their own configuration of that component).
When you say "the users expect" to have a given component have a different owner, depending on what stream is sharing it, why do they expect that? What are they hoping to achieve by having that be the case?
Comments
https://jazz.net/forum/questions/195969/component-reuse-in-another-pa
So how to share the component A with PA1 and PA2?
In order to make component A visible to all members of PA1 and PA2, some of your choices include:
- make a user the owner of component A, and set the Visibility to Public (this is simplest, but it means everyone who has access to the repository can see that component)
- create a new team area (in either PA1 or PA2), add all of the members of PA1 and PA2 to this new team area, set this team area as the owner of component A, and set the visibility of the component to be this team area.
- create a new project area, add all of the members of PA1 and PA2 to this new project area, and set this project area as the owner of component A.
Note that in 6.0.1, things should get simpler. The current plan is to allow you to define an Access Group that contains PA1 and PA2, and then you can just make the owner of component A be that Access Group.
Hi Geoffrey, I appreciate your answers/comments.
Comments
Arne Bister
JAZZ DEVELOPER Jul 04 '15, 10:21 a.m.The basic SCM paradigm in RTC allows you to reuse Component A as the same object in Stream B. The stream histories are separated so that if people in PA1 introduce changes on Stream A on Component A these changes will NOT be visible in PA 2 on Stream B (unless explicitely delivered) and vice versa.
Why do you want to clone Component A and have PA2 assigned as the owner. Is security or visibility your concern? Which use case do you want to execute that you think requires a component cloning?
Taki Nakajo
Jul 06 '15, 2:24 a.m.Taki Nakajo
Jul 06 '15, 2:24 a.m.Project Area 2
Taki Nakajo
Jul 06 '15, 2:25 a.m.Taki Nakajo
Jul 06 '15, 2:25 a.m.Project Area 1
Taki Nakajo
Jul 06 '15, 2:26 a.m.Can we do that?