Hello Ralf,

to my understanding there is no connection between plans and streams other
than may be both being related to the same team. In RTC 2.0 a work item can
be presented on different plans too.

It would probably be possible do create an extension to jazz that creates
such an automation. I don't know of one as of today. You could identify a
work item on one plan using the "planned for" attribute value which determines
for which iteration it is planned. I guess you can figure the development
line from there and deterime if the stream to deliver to is owned by a team
on that development line. The jazz.extends forum would be a good idea to
ask. Another option may be a work item if you think this is important.

One thought on this topic however: if such a mechanism would be in place
it would be impossible to merge a change from one stream into the other at
least for all roles with the restriction being in place.


Ralph

We have two iteration plans with parallel work (1: development and 2:
bugfix of a release > snapshot). Therefor we have two streams
(each belongs to one of the iteration plans). Is it possible to link
a stream to a iteration plan (so in stream 1 you can only check in
files with an task of iteration plan 1, and in stream 2 only in
iteration plan 2).
Thanks.

ralf.ovelgoenne wrote:

We have two iteration plans with parallel work (1: development and 2:
bugfix of a release > snapshot). Therefor we have two streams
(each belongs to one of the iteration plans). Is it possible to link
a stream to a iteration plan (so in stream 1 you can only check in
files with an task of iteration plan 1, and in stream 2 only in
iteration plan 2).

There is no explicit link between stream and plans. To achieve what you
are asking for, you should check out the follow-up actions for the
deliver operation. If you have two different team, you can restrict who
is able to deliver to a stream.


--
Cheers, Johannes
Agile Planning Team