It's all about the answers!

Ask a question

Compoenent Search by Stream


Canberk Akduygu (99237371) | asked Jun 15 '11, 10:36 a.m.
Hi,

We have several project where some components are used in more than one stream. There is a 1-n relationship between components and stream. Is there a way to identify component-stream relation?(Like having a picture of the component-stream map). or would you suggest me a work around?

We are now keeping excel files for that.

3 answers



permanent link
Tim Mok (6.6k38) | answered Jun 15 '11, 11:12 a.m.
JAZZ DEVELOPER
Hi,

We have several project where some components are used in more than one stream. There is a 1-n relationship between components and stream. Is there a way to identify component-stream relation?(Like having a picture of the component-stream map). or would you suggest me a work around?

We are now keeping excel files for that.
What do you plan to do with this information? There currently isn't a way to find all the streams/workspaces where a component has been added.

This seems like an odd bit of information to look up. It would be good to know what the whole use case is to see if a similar use case can fulfill this requirement or if an enhancement is required.

permanent link
Canberk Akduygu (99237371) | answered Jun 16 '11, 6:01 a.m.
What do you plan to do with this information? There currently isn't a way to find all the streams/workspaces where a component has been added.

This seems like an odd bit of information to look up. It would be good to know what the whole use case is to see if a similar use case can fulfill this requirement or if an enhancement is required.


Use case is that we have more than 100 component. And there are different projects. Some components are used in parallel development in different projects. After making those development we have different versions of those components.

Time to time like after production deployment we may like to merge those components. But as we can't keep the track of componets versions it is difficult tofind what we are looking for. That's why we need a component-stream relation mapping. may be the way we are trying to achvive the problem is wrong. You can shows a "smart way" to do it.

And also is there a way to show the component name on the workitem?

permanent link
Geoffrey Clemm (30.1k33035) | answered Jun 16 '11, 8:45 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I would suggest the following:

Identify a stream as the "integration" stream, into which all changes
for the components should flow.
Whenever you create a new stream that will contain changes that should
flow into the integration stream, add that stream to the flow targets of
the integration stream (you can do that in the Stream editor).

When you are ready to make sure all changes have been delivered into the
integration stream, load the integration stream into the Pending Changes
view, and in the Changes preference page, select "Flow Targets: Show All
(advanced)". This will show all of the streams in the Pending Changes
view, and you can reasonably easily see whether there are any orphan
changes that have not yet been delivered to the integration stream (and
in fact, if there are no conflicts can cause them to be delivered,
directly from the Pending Changes view).

Cheers,
Geoff


On 6/16/2011 6:08 AM, canberk wrote:
tmokwrote:
What do you plan to do with this information? There currently isn't a
way to find all the streams/workspaces where a component has been
added.

This seems like an odd bit of information to look up. It would be
good to know what the whole use case is to see if a similar use case
can fulfill this requirement or if an enhancement is required.

Use case is that we have more than 100 component. And there are
different projects. Some components are used in parallel development
in different projects. After making those development we have
different versions of those components.

Time to time like after production deployment we may like to merge
those components. But as we can't keep the track of componets
versions it is difficult tofind what we are looking for. That's why
we need a component-stream relation mapping. may be the way we are
trying to achvive the problem is wrong. You can shows a "smart
way" to do it.

And also is there a way to show the component name on the workitem?

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.