Transferring an issue to another repository
To move an issue to a better fitting repository, you can transfer open issues to other repositories.
To transfer an open issue to another repository, you must have write permissions on the repository the issue is in and the repository you're transferring the issue to. If you're transferring an issue from a repository that's owned by an organization you're a member of, you must transfer it to another repository within your organization. You can't transfer an issue from a private repository to a public repository. For more information, see "Repository permission levels for an organization."
When you transfer an issue, comments, assignees, and issue timeline events are retained. The issue's labels, projects, and milestones are not retained, although you can see past activity in the issue's timeline. People or teams who are mentioned in the issue will receive a notification letting them know that the issue has been transferred to a new repository. The original URL redirects to the new issue's URL. People who don't have read permissions in the new repository will see a banner letting them know that the issue has been transferred to a new repository that they can't access.
Transferring an open issue to another repository
On GitHub, navigate to the main page of the repository.
Under your repository name, click Issues.
In the list of issues, click the issue you'd like to transfer.
In the right sidebar, click Transfer issue.
Use the Choose a repository drop-down menu, and select the repository you want to transfer the issue to.
Click Transfer issue.