component is orphaned

Edwin Lukaweski (6●2●2) | asked Oct 14 '08, 1:54 p.m.

I have gotten into a situation whereby some components seem to be "orphaned". They have been removed from a stream and workspace. So, I see them in the results of a component search, but cannot seem to access them when I "add" a component to a workspace, since they do not exist as part of another workspace or stream.

An answer would really be appreciated.

Does anybody have any ideas on how to "un-orphan" these components? Thanks

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0	permanent link William Byrne (55●4●5) \| answered Feb 13 '10, 3:52 a.m. Experiencing same problem. No obvious way to eliminate it.

permanent link

Geoffrey Clemm (30.1k●3●30●35) | answered Feb 13 '10, 10:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

When you invoke the "add component" operation, select the "Component
Baseline" option, and you are given the list of all components to which
you have read access. Make sure you have read access to the component
of interest, and that it is not a "private" component (i.e. a component
owned by a user, not a team area).

Cheers,
Geoff

elukaweski wrote:

I have gotten into a situation whereby some components seem to be
"orphaned". They have been removed from a stream and
workspace. So, I see them in the results of a component search, but
cannot seem to access them when I "add" a component to a
workspace, since they do not exist as part of another workspace or
stream.

Does anybody have any ideas on how to "un-orphan" these
components? Thanks

Your answer

Register or log in 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.

It's all about the answers!

Related questions

component is orphaned

2 answers

Your answer