Repercussions of moving a team structure under a new team in
I am trying to figure out what would be the repercussions of moving an existing team structure from one development line to a different one. Would there be any ill-effects? Would we still be able to open and view plans that were created for those teams in the older development line? It seems like a safer thing for me to do is to just create new teams in the newer devleopment line rather than moving the older teams there. (This new development line will be our main development line).
|
One answer
Hi Patrik,
unfortunately the plans would disappear from the TAN and currently you wouldn't have a function to find them again, unless you move the team areas back to the old development line. The reason is that a plan is created for a Team Area / Iteration tuple and if you move the team area to a different dev line the team area is associated with a different set of iterations and hence our query wouldn't find the plans. A work around of the problem is as follows: mark all plans on under the old development line as a favorite (move them into the favorite folder using D&D). Move the team areas to the new dev line. Execute Configure Plan... from the context menu for all plans in the favorite folder and set the iteration to the iteration of the new dev line. Dirk Bumer Agile Planning Component Pratik Shah wrote: I am trying to figure out what would be the repercussions of moving an |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.