Sounds like a bug in copy teams functionality. Each object including
iterations have their own team. The team is initialized from predecessor
and or container teams. Make sense?
On Feb 5, 2015 12:01 PM, "Haigh, David A." <->
wrote:
> Note: Due to the attachment size(s), links to download the attachment(s)
> for this email have been provided at the bottom.
>
> At some point in the past the behavior of our 9.1-m070 system changed.
> (We’ve had this system since 8.0-m020)
>
> We think there is some configuration that we must have wrong in our
> system. Any ideas appreciated.
>
>
>
> What’s happening now is team membership for objects is not showing the
> groups. It’s showing the individuals in the group.
>
>
>
> If we look at an old iteration of an object and look at Collaoration Team,
> you see the groups listed:
>
> [image: cid:image003.png@01D04091.49A7E580]
>
>
>
> If you look at a new iteration of the same object you don’t see the
> groups, you see the members of the group.
>
> [image: cid:image004.png@01D04091.49A7E580]
>
>
>
> Adding members to the group does not allow those new members to see the
> newer iterations of the files.
>
>
>
> If you go to a specific iteration and pick Actions, Reset Team, the new
> users show up in the list.
>
>
>
> Now go look at what iterations that user can see and you will see a gap in
> the iteration history.
>
>
>
> [image: cid:image006.png@01D04091.49A7E580]
>
>
>
> David Haigh
> Phone: 925-424-3931
> Fax: 925-423-7496
> Lawrence Livermore National Lab
> 7000 East Ave, L-362
> Livermore, CA 94550
>
>
>
