Reuse the existing component in a new stream in a new project
![]()
When you want to re-use the existing component from the old project's steam, how can you create a new steam?
Project Area 1
|- Steam A
|- Component A ( Baseline 123 )
Project Area 2
|- Steam B
|- Component A (Baseline 123 )
If I duplicate the steam A from the project 1 to the new Steam B, the component A is still owned by the project 1 since it is the same instance. If I change to the new project area 2 as a owner of the component, the owner of the component A in the steam A is also the project are 2.
How can I independently create a new component from the component A's baseline, assign the project 2 as the owner?
showing 5 of 6
show 1 more comments
|
Accepted answer
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 06 '15, 7:29 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
As indicated by Arne, a component is not "owned" by a stream, it is "shared" by a stream.
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? Taki Nakajo selected this answer as the correct answer
Comments
When a user 2 is a member of the only PA2, then if I add Component A in stream B in PA2. the user 2 in the PA2 cannot even see the component A since the ownership/visibility is still PA1.
I referred to your past answer but I'm afraid I'm not still clear.
https://jazz.net/forum/questions/195969/component-reuse-in-another-pa So how to share the component A with PA1 and PA2? ![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In order to make component A visible to all members of PA1 and PA2, some of your choices include:
Hi Geoffrey, I appreciate your answers/comments. |
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.
Comments
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?
Project Area 2
Project Area 1
Can we do that?