-
-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Object reference not set to an instance of an object #816
Comments
Issue seems to be happening when links are added to revisions, as in revision 2 of the given work item. Not yet enough data to reproduce the issue |
Issue is one our side, we are only migrating a subset of jira issues |
see above comment |
Reopening so we can look at creating a more specific error message. To reproduce: migrate only a subset of jira issues where one issue has a link to an issue outside the migrated set. |
@RoyalWulf Thanks for discovering this one :) |
Describe the problem
A clear and concise description of what the problem/bug is.
[I][19:18:32] Processing 38087/57276 - wi '64071', jira 'US-26430, rev 2'.
[E][19:20:12] Object reference not set to an instance of an object.
[W][19:20:12] ''US-26430', rev 2' - not all changes were saved.
To Reproduce
Steps to reproduce the behavior:
run wi-import
Tool version
3.0.139
Attachments
Please attach the following files:
config-agile_SMS3 - Copy.json.txt
[wi-import-log-230721-155604.txt](https://github.com/solidify/jira-azuredevops-migrator
US-26430 - Copy.json.txt
/files/12157059/wi-import-log-230721-155604.txt)
jira-export-log-230721-143348.txt
Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: