Is there any way to limit the iterations in Planned For Selection list by Team?

We are using RTC 4.0.2 and testing 5.0.2 in preparation for upgrading.  We have been noticing that in both versions, the list of iterations presented in the work item Planned For field is the complete list of iterations, regardless of what team is the selected team based on Filed Against value.  Our Work Item categories are configured such that each category is associated with a specific team, regardless of the Timeline.  Each team is associated with a different timeline.  However, whenever we go into a work item and select a Filed Against value to specify a team, the list of iterations in the Planned For field comes from every timeline, not just the timeline associated with the identified team.  This does 2 things, first it allows selection of iterations that do not make any sense for the Filed Against selected team.  Second, it presents a huge list of mostly inaccurate iteration choices to users.

I found references to an article that gives an overview of RTC Project Fundamentals: https://jazz.net/library/article/589 .  In this article under Planning a Work item for an Iteration, it states "The work item can only be planned for an iteration belonging to the timeline the owning team is working against".  This is exactly what we want, but don't see happening.  Are we missing something in our project configuration, or did this behavior change at some point after the article was written?

Thank you,
Jamie.