AreaPaths & IterationPaths not being mapped #2530
Unanswered
jam1efrancis
asked this question in
Q&A
Replies: 1 comment 3 replies
-
|
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
Running version 16.0.7.
I've been able to successfully perform a test migration and almost everything is working perfectly. I think I must have a configuration issue though because I can't seem to get the tool to map the iteration or area paths. Whilst I could manually do this it would be preferable to be able to have the tool do it, as i've got quite a lot of work items to migrate.
For clarity, I'm migrating from one organisation to another, with a full access PAT specified for each. The process is changing from a custom Scrum to Agile (all default except the reflectedworkitemid field).
This is my FieldMaps section from configuration.json, names of area paths changed due to proprietary info.
When the migration runs, this is the output relating to this part of the config - it seems to be ignoring it. Have I got something wrong?
It also creates the sprints under
\myproject\Iteration
but it should be undermyproject\MyApp\
.Note that the
WorkItemTypeMappingTool
IS working correctly but this is in a different section of the configuration.json file.TfsWorkItemMigrationProcessor
settings - I've limited the scope to a few work items for testing purposes. I would appreciate any advice about theNodeBasePaths
property as I think this may be causing some issues. It's hard to find an answer about what I put there, but it seems to match my source environment.Thanks in advance, let me know if I need to provide any more info but this is basically my entire config other than setting the source/target Azure DevOps locations.
Beta Was this translation helpful? Give feedback.
All reactions