Areas and iterations not sync'ing

[Bruce]

Set up some new areas and iterations in a new project, they aren't coming across to TFS.

Is there a setting to set them to sync?

Thanks for your help.

[Ryan]

Hello Bruce,

Areas and iterations will be created in TFS or TeamPulse as needed to support stories assigned to those areas or iterations. For example, if you assign a story to an area in TeamPulse then sync that story with TFS, the area for that story will be created in TFS at this point if it doesn't already exist.

All the best,
Ryan
the Telerik team

[Bruce]

Thanks for the quick response -  I'm thinking an explanation of what sync's and when it sync's would be useful in help.

I'm liking the product, just posting lots of questions to figure out the details.

[Jonathon Stevens]

This isn't a good way to sync in my opinion.  What's going to happen when we have a bunch of areas and iterations we've created in TFS (I have a templated set of areas and iterations that are built each time we build a new team project) and want to assign stories to those for the first time?  Can't you guys have TeamPulse grab the Areas/Iterations from TFS and vice versa after they are created and not just when they are used in a story?

[David Harris]

Hello Jonathon Stevens,

We have a product backlog item logged in regards to performing a first-time pull of areas and iterations from TFS into TeamPulse when connecting to deal with the specific issue you mention however it has not yet been scheduled for development. We will take your feedback into consideration for prioritization in future releases.

Regards,
David Harris
the Telerik team

[Jonathon Stevens]

David,

Thank you for the response.  My suggestion isn't a 'one-time' sync initially, but have it be part of the syncing process to check TFS and TP for modifications to the area/iterations.  I would also suggest a template of areas based on different needs as part of the initial project setup.

[David Harris]

Hello Jonathon Stevens,

The process of synchronizing area and iteration trees continuously is ideal for many and was certainly something we discussed at length when implementing our TFS integration solution. Unfortunately when dealing with TFS it is very difficult to know when an iteration or area has been renamed or moved (versus simply deleted), which presents many problems for synchronization. Furthermore, TeamPulse provides the ability to synchronize multiple TeamPulse projects with one TFS project via the use of different synchronization queries. These scenarios are common in larger enterprises (including Telerik internally) and are generally segregated by area and/or iteration. In these scenarios a continuous and full sync of areas and iterations apart from work items is not desirable at all.

In regards to initial project area templates this is a good idea and something I will add to our backlog. With our next release we have implemented some functionality designed to enhance project creation, however area setup is not currently part of our designs. This may be something we can do to further enhance this new functionality down the line. I have applied some Telerik points to your account as a form of thanks.

Regards,
David Harris
the Telerik team