This question is locked. New answers and comments are not allowed.
I renamed several interations in Team Pulse, assigned story's to them and when I look at in TFS all reports fail because it doesn't see the new interation names.
Thanks,
Joe
Thanks,
Joe
3 Answers, 1 is accepted
0
Hello Joe,
Hi Joe,
I think I'll need a bit more information to narrow this one down. Can you tell me if your iteration name-changes synced correctly? So now when you look in both TeamPulse and TFS, the iterations have the same name? If not, are there Sync Errors within TFS?
If the changes did sync correctly, can you extrapolate on what you mean when you refer to TFS Reports? Are these simply user queries that are keying on a specific iteration name? Or is this something else?
Once we have a bit more detail on the situation we can likely determine how to act on it.
Regards,
David Harris
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Hi Joe,
I think I'll need a bit more information to narrow this one down. Can you tell me if your iteration name-changes synced correctly? So now when you look in both TeamPulse and TFS, the iterations have the same name? If not, are there Sync Errors within TFS?
If the changes did sync correctly, can you extrapolate on what you mean when you refer to TFS Reports? Are these simply user queries that are keying on a specific iteration name? Or is this something else?
Once we have a bit more detail on the situation we can likely determine how to act on it.
Regards,
David Harris
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
Joe
Top achievements
Rank 2
Rank 2
answered on 22 Apr 2010, 08:36 PM
Iteration names are in both places.
I do have two Sync errors that will not go away. The first one was because I changed an iteration to "April/May" and TFS didn't like it. I have since renamed the interation but the Sync error is still there.
THe second Sync error is at "Root Nodes cannot be modified" I cannot attach a screenshot of the Sync error page in this forum. Here's the full error (please fix the upload to this forum, it's a lot to type).
Microsoft.TeamFoundation.Server.CommonStructureSubsystemException: TF200021: The foloowing node is a root node: vstfs:///Classification/Node/a235b758-6888-4783-8472-1471418ea1df. Root nodes cannot be modified.
at Microsoft.TeamFoundation.Proxy.CommonStructureService.RenameNode(String nodeUri, String newNodeName)
at Synchronization.TFS.Engine.TfsSynchronizer.UpdateIterationDTO iterationToUpdate)
You are also correct that the standard queries are broken in TFS. I can modify the query and the Report will run.
Thanks,
Joe
I do have two Sync errors that will not go away. The first one was because I changed an iteration to "April/May" and TFS didn't like it. I have since renamed the interation but the Sync error is still there.
THe second Sync error is at "Root Nodes cannot be modified" I cannot attach a screenshot of the Sync error page in this forum. Here's the full error (please fix the upload to this forum, it's a lot to type).
Microsoft.TeamFoundation.Server.CommonStructureSubsystemException: TF200021: The foloowing node is a root node: vstfs:///Classification/Node/a235b758-6888-4783-8472-1471418ea1df. Root nodes cannot be modified.
at Microsoft.TeamFoundation.Proxy.CommonStructureService.RenameNode(String nodeUri, String newNodeName)
at Synchronization.TFS.Engine.TfsSynchronizer.UpdateIterationDTO iterationToUpdate)
You are also correct that the standard queries are broken in TFS. I can modify the query and the Report will run.
Thanks,
Joe
0
Hi Joe,
Thank you for the information regarding the sync errors. We have had the 'Root Nodes cannot be modified' error previously reported, and have logged it internally. As for the error that will not go away, we are aware of this issue with some sync errors. We are doing some major work on the sync engine in the weeks between now and full release and will definitely look into overcoming these problems.
As for the TFS queries, unfortunately I believe this is out of our control. I believe the same problem would occur if you were to rename your iterations directly within TFS itself.
Regards,
David Harris
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Thank you for the information regarding the sync errors. We have had the 'Root Nodes cannot be modified' error previously reported, and have logged it internally. As for the error that will not go away, we are aware of this issue with some sync errors. We are doing some major work on the sync engine in the weeks between now and full release and will definitely look into overcoming these problems.
As for the TFS queries, unfortunately I believe this is out of our control. I believe the same problem would occur if you were to rename your iterations directly within TFS itself.
Regards,
David Harris
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.