"Cannot call "ez" on null" when it tries to close the original issue

[Daniel15]

I just encountered this error:

The issue and all its comments were copied across okay, I just had to manually close the original issue.

[vrad-exe]

I've found that this only happens when moving an issue from a repository on an organization. I get the error when moving issues from BEEmod/BEE2.4 to BEEmod/BEE2-items. However, when I previously moved a few issues from another user's fork to BEE2-items this error did not occur.

[tamalsaha]

I am also seeing this issue. It will be nice have this fixed.

[PatrickvL]

Same thing happened to me too; After moving dozens of issues, I seem to had hit a quota limit or something, because I got the above reported error. After waiting a few minutes, I could move another batch until I got the same error again. I waited another while, after a few hours I could move another batch. But once I reached 150 moves, it stopped working altogether. I've waited for 3 days already now, but it still won't move a single issue anymore.

Edit : I was moving these to here.

Also it wasn't resolved by clicking 'logout' and on the next page 'Authorize GitHub' buttons.

[vrad-exe]

@PatrickvL Your issue is a bit different, the issue described here is that it failed to close the original issue - everything copied over fine, you just need to close the original issue manually. I've experienced your bug before, however, when trying to move a large issue (specifically this one) to BEE2-items. I ended up having to copy the issue manually.

[gubuntu]

I also get this error, but it doesn't even get as far as creating the new issue

That's on Chrome.

On Firefox the error is Error creating new issue: NullError: J.w1(...) is undefined

[TimvdLippe]

Crossposting here from #121:

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.