-
|
Hello, I am getting the error mentioned below. |
Beta Was this translation helpful? Give feedback.
Answered by
MrHinsh
Nov 13, 2023
Replies: 8 comments 30 replies
-
|
As per the documentation, you need to add Iteration Maps and Area Maps that adapt the old locations to new ones that are valid in the Target. Before your migration starts it will validate that all of the Areas and Iterations from the Source work items revisions exist on the Target. Any that do not exist will be flagged in the logs and the migration will stop just after it outputs a list of the missing nodes. Our algorithm that converts the Source nodes to Target nodes processes the mappings at that time. This means that any valid mapped nodes will never be caught by the
To add a mapping, you can follow the documentation with this being the simplest way: Or you can use regular expressions to match the missing area or iteration paths: If you want to use the matches in the replacement you can use the following: If the olf iteration path was Regular expressions are much more difficult to build and debug so it is a good idea to use a regular expression tester to check that you are matching the right things and to build them in ChatGTP. NOTE: You need
|
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
MrHinsh
-
|
Hi @MrHinsh , Sorry but I have no idea about the Iteration and Areas in ADO. Any links to learn about these and where can I locate these on ADO? Thanks for help ! It looks like this:
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
@RSwarnkar this tool is designed for experts in Azure DevOps. Do you have someone locally that can help you? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Should I use below config @MrHinsh
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
The replacement format is listed on https://nkdagility.com/learn/azure-devops-migration-tools/howto/creating-iteration-and-area-maps/ |
Beta Was this translation helpful? Give feedback.
-
|
Ok, trying with this now: |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Ok, Its working |
Beta Was this translation helpful? Give feedback.
-
|
Most of your mappings are unessesary as the "out of the box" functionality maps old project to new project. You only need an explicit mapping for:
|
Beta Was this translation helpful? Give feedback.
-
|
I have updated my config in similar way where in i have my Iterations as below and in my destination i have created only one sub path and mapped it in the config, but when i run the migration it is creating all the Areas and Iterations which are in source, i dont want to have those in my destination. @RSwarnkar / @MrHinsh : Can anyone suggest what am i missing here, by the way i am using "Version": "16.0" Source Details:
Destination Details: Config Maps: |
Beta Was this translation helpful? Give feedback.
9 replies
-
|
@MrHinsh I have attached the log file for reference, can you please take a look once |
Beta Was this translation helpful? Give feedback.
-
|
@Chandu001729 ive added some extra logging to see what the issue is on your site: If I can only assume that public void ProcessorExecutionBegin(TfsProcessor processor)
{
Log.LogDebug("TfsNodeStrictureTool: Enabled={enabled}", Options.Enabled);
if (Options.Enabled)
{
EntryForProcessorType(processor);
Log.LogDebug("TfsNodeStrictureTool: ReplicateAllExistingNodes={ReplicateAllExistingNodes}", Options.ReplicateAllExistingNodes);
if (Options.ReplicateAllExistingNodes)
{
Log.LogInformation("Migrating all Nodes before the Processor run.");
MigrateAllNodeStructures();
RefreshForProcessorType(processor);
} else
{
Log.LogInformation("SKIP: Migrating all Nodes before the Processor run.");
}
}
else
{
Log.LogWarning("TfsNodeStructureTool: TfsNodeStructureTool is disabled! This may cause work item migration errors! ");
}
} |
Beta Was this translation helpful? Give feedback.
-
|
Note also that |
Beta Was this translation helpful? Give feedback.
-
|
Hi @MrHinsh , need your assistance, with the latest code that you have committed #2654, i have ran the migration again and observed the same issue that the all the Iterations are getting created in the Destination. Output Log: |
Beta Was this translation helpful? Give feedback.
-
|
@MrHinsh need your assistance, i have used the latest code which was updated |
Beta Was this translation helpful? Give feedback.
-
|
@MrHinsh with the latest code that you have committed #2654, i have ran the migration again and observed the same issue that the all the Iterations are getting created in the Destination. |
Beta Was this translation helpful? Give feedback.
10 replies
-
|
It looks like your Source is setup as "Team Field" which is not supported on Azure DevOps. You need to revert to Area Path before you migrate. |
Beta Was this translation helpful? Give feedback.
-
|
@MrHinsh not getting like what need to be changed, any link to identify the things. I have the screenshots of my Source and Destination Area and Iteration details in the above conversation Current Area: |
Beta Was this translation helpful? Give feedback.
-
|
@MrHinsh But we are not using the TFS it is a Azure DevOps ADO only |
Beta Was this translation helpful? Give feedback.
-
|
Can you check that every team has the team fields set? You can open the configuration for each team. Its likely that a team field has an invalid value as the Area path has been deleted. |
Beta Was this translation helpful? Give feedback.
-
|
@MrHinsh I have validated in the source and Destination side and all the configurations have the Area maps updated. I am not getting like what else need to be validated in this case. Source Team 1:
Source Team 2:
Destination Team 1:
Destination Team 2:
Destination Team 3:
|
Beta Was this translation helpful? Give feedback.
7 replies
-
|
@MrHinsh All Area paths set for teams exist in both sides, i have attached those screenshots above. I am not using that Module in my config at all, i have only the TfsNodeStructureTool. Do i need to add that module and make it as false, so that it wont pick those or how it works.? |
Beta Was this translation helpful? Give feedback.
-
|
The documentation shows the "defaults" that are applied. |
Beta Was this translation helpful? Give feedback.
-
|
@MrHinsh I have added that module and disabled it and it is going through, but we have already mapped the Area paths and it is giving that these Areas are missing in the Destination side. It was supposed to map everything based on what we have provided in the config right.? Config: Error: |
Beta Was this translation helpful? Give feedback.
-
|
The area paths in the log that are listed as not mapped are not mapped by the config that you presented. This is the correct behaviour. |
Beta Was this translation helpful? Give feedback.
-
|
@MrHinsh So instead of defining it for every area path, i can define it like same as Iteration paths right which can take everything or can you show a sample config or one Area path map from above which i can use for Area path, which will help me to map the things. |
Beta Was this translation helpful? Give feedback.
-
|
@Chandu001729 please create new topic. I think I am getting too much notifications. Thanks :) |
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
As per the documentation, you need to add Iteration Maps and Area Maps that adapt the old locations to new ones that are valid in the Target.
Before your migration starts it will validate that all of the Areas and Iterations from the Source work items revisions exist on the Target. Any that do not exist will be flagged in the logs and the migration will stop just after it outputs a list of the missing nodes.
Our algorithm that converts the Source nodes to Target nodes processes the mappings at that time. This means that any valid mapped nodes will never be caught by the
This path is not anchored in the source projectmessage as they are already altered to be valid.