Replies: 1 comment
-
By default the old project name is always adapted to the new project name. You only need to add mappings if you have things we don't know how to map. In the error is a link to the documentation oh how to create the mappings. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi! I am getting error trying mapping Area and Iteration path. I am trying to migrate items from a source KANBAN project which were move from another SCRUM proyect to another target KANBAN project which is in another organization.
The problem is when I execute the migration script I get an error saying "It is NOT possible to migrate a work item if the Area or Iteration path does not exist on the target project" this is because the items are taking the SCRUM Area or Iteration path instead the source KANBAN project....
I am trying to mapping the very first SCRUM project Area or Iteration path from the source KANBAN project to the new target KANBAN project, but I do not know if this is OK....
I show you my config...
`{
"Serilog": {
"MinimumLevel": "Information"
},
"MigrationTools": {
"Version": "16.0",
"Endpoints": {
"Source": {
"EndpointType": "TfsTeamProjectEndpoint",
"Collection": "https://dev.azure.com/Org1/",
"Project": "Project1",
"Authentication": {
"AuthenticationMode": "AccessToken",
"AccessToken": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
},
"LanguageMaps": {
"AreaPath": "Area",
"IterationPath": "Iteration"
},
"EndpointEnrichers": null
},
"Target": {
"EndpointType": "TfsTeamProjectEndpoint",
"Collection": "https://dev.azure.com/Org2/",
"Project": "Project1",
}
}`
Beta Was this translation helpful? Give feedback.
All reactions