Not able to migrate shared queries where are and iteration paths are different. #2700
Unanswered
sanc001997
asked this question in
Q&A
Replies: 2 comments
-
@MrHinsh Please help |
Beta Was this translation helpful? Give feedback.
0 replies
-
Have you followed https://nkdagility.com/learn/azure-devops-migration-tools/Reference/Processors/TfsSharedQueryProcessor/ and created "SourceToTargetFieldMappings" for field differences? Im almost positive the ObjectModel does not support "@currentiteration" |
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
-
I am facing issues while migrating Shared Queries. The "TfsSharedQueryProcessorOptions" processor is looking for default areapaths and iterations that tool creates but not using the filed mapping defined in configuration file.
Could you please help with the configuration for migrating Shared Queries when the source and target areapaths and iterations are different.
error
Error saving query 'Incomplete Work in Old Sprints', probably due to invalid area or iteration paths
Microsoft.TeamFoundation.WorkItemTracking.Client.InvalidQueryTextException: TF51015: The add or subtract operators can only be used with dates or numerical constants. The error is caused by «@currentiteration + 2». ---> Microsoft.TeamFoundation.WorkItemTracking.Client.Wiql.SyntaxException: TF51015: The add or subtract operators can only be used with dates or numerical constants. The error is caused by «@currentiteration + 2».
Beta Was this translation helpful? Give feedback.
All reactions