TFS Sync Errors & Conflicts Never Resolved

4 posts, 0 answers
  1. Chris Adams
    Chris Adams avatar
    29 posts
    Member since:
    Nov 2009

    Posted 06 Dec 2011 Link to this post

    All-

    We have a single problem on a single project where we continue to get massive amounts of errors in Team Pulse when sync'ing.  The errors are always relating to invalid iteration -

    Error updating Story #### in Team Pulse.  Error:  Could not find iteration with path Project\OpsLight Quality\Sprint 5.

    However, this exists on both sides in TFS & TeamPulse.  This happens for every net new work item, whether story, task that is added to this project within TeamPulse or TFS.

    I'd like any help in figuring out what is the magic bullet to debug this.  I can't figure it out.

    Thanks
    -Chris
  2. David Harris
    Admin
    David Harris avatar
    1 posts

    Posted 07 Dec 2011 Link to this post

    Hi Chris Adams,

    I believe you may have encountered a bug in which our sync process is inconsistent with our UI rules. The issue is that the sync process currently assumes that the root iteration is named "Project", which is the default when a new project is created in TeamPulse. However, the TeamPulse UI allows you to modify this value, which it appears you have done based on your description of your iteration tree.

    Can you please try using the TeamPulse UI to rename your root iteration back to "Project", and then attempt a synchronization with TFS? I have attached a screenshot of our internal iteration tree showing how it should look. No changes should be required in TFS as the root iteration is always simply the name of the project.

    Please let us know if this resolves your issue. If this is indeed the problem, we will log a bug against the sync service of high priority in order to get this inconsistency resolved for the next release.

    Regards,
    David Harris
    the Telerik team
    New TeamPulse release is here!
    Want to know what’s New and how TeamPulse could help you better tight with your clients?
    Reserve a seat for the TeamPulse R3 Webinar today!
  3. Chris Adams
    Chris Adams avatar
    29 posts
    Member since:
    Nov 2009

    Posted 07 Dec 2011 Link to this post

    Hey David-

    That was the problem.  After renaming the root from MPSD Dev SE to Project, all conflicts and errors went away.  I also checked other projects that were working and this was what was different.  I missed this :)

    I hope that you can eventually support this or at least remove the F2 rename support from the root so folks can't break themselves.

    With that said, consider this matter closed :)

    Thanks,
    -Chris
  4. David Harris
    Admin
    David Harris avatar
    1 posts

    Posted 08 Dec 2011 Link to this post

    Hi Chris,

    Thanks for the update. I have logged the bug and awarded you some Telerik points for your troubles.

    All the best,
    David Harris
    the Telerik team
    New TeamPulse release is here!
    Want to know what’s New and how TeamPulse could help you better tight with your clients?
    Reserve a seat for the TeamPulse R3 Webinar today!
Back to Top