Open steveswinsburg opened 8 years ago
Actually it may be that the user is not in the destination repo. In this case it might be good if the assignee was removed, so that the issues can be migrated.
I encountered this issue. In my case, an issue on repo 1 was assigned to X. I wanted to move this issue to repo 2, in which X no longer was a member. The "move issue" button then returned "Can not retrieve "ez" of null" and the network tab showed a 422 unprocessable entity. Removing the assignment of X in repo 1 and trying to the move again fixed the issue.
I am moving a bunch of issues from a repo where I am the owner. However I have a collaborator in that repo and some issues are assigned to him. These cannot be moved. I first need to remove the assignee then I can move them.