-
This is for issues: For questions on usage please use https://stackoverflow.com/questions/tagged/azure-devops-migration-tools and tag with Describe your issue:I'm attempting to migrate a project from our on-prem ADOS to ADO (cloud), and succeeded, partially. It seems the Closed work items did not migrate. I've checked my config file, and I don't have the qualifier to check for ClosedDate = ''. I even specifically added a check where ClosedDate != '' in the query bit, and it still did not find the closed Work Items when I tried re-running the script. I'm running v11.9.29.0 of the tool. However, when running the script, I see this query in the logs:
Describe any Exceptions:No Exceptions Source Details
Target Details
I have completed the following:
Log file: migrate.log Config file: Many issues are due to edge cases and will need debugging in Visual Studio; we cant do that for you on your environment. |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 1 reply
-
In attached config you are skipping WI that have
Use
|
Beta Was this translation helpful? Give feedback.
-
I'll try this when I'm back in the office at work, thank you! I got the != from an SO thread, and thought SQL still treated it as <>. My initial config didn't even include that piece in the query bit, so why would it have not migrated closed items to begin with? |
Beta Was this translation helpful? Give feedback.
-
I would not worry about it, unless you have logs and config of initial run. So many issues ahead no reason to worry about past ones 😎 |
Beta Was this translation helpful? Give feedback.
-
I changed the Log line:
QueryBit from config:
|
Beta Was this translation helpful? Give feedback.
-
Hello @carnageX I got the same issue than you with :
Did you found any workaround/solution to this problem ? |
Beta Was this translation helpful? Give feedback.
-
No unfortunately I have not. |
Beta Was this translation helpful? Give feedback.
-
here is my work around : Querry all the task that are in done state, then tag them with something unique, change the state to something else then run the migration. Hoppefully this will help ! |
Beta Was this translation helpful? Give feedback.
-
@carnageX you have "QueryBit" instead of "WIQLQueryBit". Internally if "WIQLQueryBit" is not set then it is left as the default query. |
Beta Was this translation helpful? Give feedback.
@carnageX you have "QueryBit" instead of "WIQLQueryBit".
Internally if "WIQLQueryBit" is not set then it is left as the default query.