Deliver to stream owned by parent team as child team member?

We have a team which has the following team area hierachy:
Team Area A
SubTeam Area a
Subteam Area b
User xxx is member of "SubTeam Area a" with contributor role
but not in the parent Team Area A

The stream is owned by Team Area A and the Visibility is set to the
Project Area.

The permission setting in Team Area A is set to allow contributors to
deliver change sets to stream and is inherited by the child team
areas.

What happened is that we found user xxx couldn't deliver change sets
to the stream owned by Team Area A until we added him to Team Area
A.

So it looks like the rule is that only members of the team area with
proper role can deliver change set to the stream owned by the team
area.

We thought the members of the child team should be able to do the
deliver too.

Is this expected behaviour?

If the stream is owned by the project area, then you do have to have a
role in the project area that allows you to deliver to that stream.

Cheers,
Geoff

gmclemmwrote:
If the stream is owned by the project area, then you do have to have
a
role in the project area that allows you to deliver to that stream.

Cheers,
Geoff


Hi, Geoff,
Thanks.
In this particular case, the stream is owned by a top level team area
which has several child team areas. But the Visibility of the stream
is set to Project area wide.
The user initially only has memebership in one of the child team areas
and can't deliver to the stream. It is solved by granting the user the
membership to the top level parent team area which actually own the
stream.

But I was under the impression that if the parent team area owns the
stream, then all members of the child team areas should have
permission to deliver to the stream without have to be specifically
added to be the member of the parent team area?

Do you remember what gave you the impression that members of child team
areas would have permission to deliver to a stream owned by the parent
project/team area ? In particular, if it was some RTC documentation,
we should get that fixed.

Cheers,
Geoff