nwinant
commented
8 years ago We just ran into exactly this issue. We worked around it by renaming the "issues" repo to something else, moving the issues, and then renaming the repo back to "issues".
That approach worked well enough, although we did have to go through the old issues and modify the "This issue was moved to [org]/[repo]#1" comments. We didn't have that many issues in the source repo, so it wasn't that big a deal, but YMMV.
We have a repository named "issues" under our organization. For some reason when I try to move an issue from xyz source repo to "issues" destination repo.
Both the source and destination are private repos. It works for other repo names, but fails to recognize "issues" repo. I doubt that has to do something with thee usage of that specific name itself.