Preview version problems: working with TfsNodeStructureTool
and WorkItemTypeMappingTool
#2328
Replies: 4 comments 8 replies
-
I'm not aware of any "latest release has the Serilog problem" with the latest release... Ahh, found what you are referring to. You are likely downloading the zip file and unpacking it. This runs through different security on windows and your security is blocking those files. Solution: You need to unblock the zip before you unpck it it works... or you can unblock the individual files... its |
Beta Was this translation helpful? Give feedback.
-
Hi there, ACTION REQUIRED In order for us to help you will need to provide both the log, and the configration file that you are using. Generate and Attach Log Steps:
Your assistance is greatly appreciated! Thanks, Azure DevOps Migration Tools team |
Beta Was this translation helpful? Give feedback.
-
This is most likely a config issue. When you generate the sample configs with
If the Source and Target are both Agile then you should remove the listed sample mapping? Documenation for this is on WorkItemTypeMappingTool/) |
Beta Was this translation helpful? Give feedback.
-
Mostly this is a config issue, and I would need to see the config to comment... but its documented extensively on TfsNodeStructureTool. The sample would look like:
Likley you don't need the filters (scopes the Area and Iteration migration), and the Mpapings here assume that there are work items that have been moved from the projects The docs show both the |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying a simple migration of a project from one Azure DevOps organization to another.
I am using the v16.0.0-Preview.9 version because the latest release has the Serilog problem.
The source is based on the Agile process so I created an empty target with a process template inherited from Agile.
I pass the authentication phase but the migration fails after 3 errors comprised of 2 types:
But no item in the source is of this type and the items having this issue are User stories.
This may be related to custom iterations and areas I have in the source.
But the documentation does not seem to address the new config format.
Any help would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions