I just tried this in the current release, and it worked fine, so you
probably will want to work with Rational Support to see if they can
duplicate the behavior you are seeing.

One possibility:

When you originally assigned categories to Team B, did you do so for
"all timelines", or just for the original timeline of Team B ? If the
latter, then when you moved Team B to a new timeline, the categories
would no longer be mapped to Team B.

Note: If that is what happened, please add a comment to work item
148005, which asks that a warning message be generated when this occurs.

Cheers,
Geoff

On 11/15/2011 5:08 PM, marky wrote:

For our last release, we created a new component in a separate team
(Team B) and created a separate timeline for that component b/c it
was on a different schedule as the larger, overall team (Team A).
Now, for the next release, Team B is being synchronized with the
larger team, Team A, so it has to follow the same timeline.
Therefore, I moved Team B so it is now a sub-team of Team A, and I
planned all the work items for Team B for iterations belonging to
Team A's timeline.
Unfortunately, for all of my plans for Team A, none of the work items
for Team B are appearing. Any ideas what else I need to change to
get this to work?

Thanks,
Mark