Needs and benefits
It would be useful to have a way to transfer issues between projects for such cases like this.
Feature Description
The transferred issue should be copied to the chosen repository as a new issue. The current one should be closed with a comment specifying it was transferred. Alternatively an issue resolution state should be added to support marking the issue not as "closed" but as "transferred", reference to the new issue should be added to the old one automatically - either by injecting the reference into the body to automate the process or an activity like gitlab does it (result would be the same either way - a bridge between old and new issue).
Docs on that feature on github and gitlab:
https://docs.github.com/en/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository
https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#move-an-issue
Screenshots
Original issue
Transferred one
### Needs and benefits
It would be useful to have a way to transfer issues between projects for such cases like [this](https://codeberg.org/forgejo/forgejo/issues/3655).
### Feature Description
The transferred issue should be copied to the chosen repository as a new issue. The current one should be closed with a comment specifying it was transferred. Alternatively an issue resolution state should be added to support marking the issue not as "closed" but as "transferred", reference to the new issue should be added to the old one automatically - either by injecting the reference into the body to automate the process or an activity like gitlab does it (result would be the same either way - a bridge between old and new issue).
Docs on that feature on github and gitlab:
https://docs.github.com/en/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository
https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#move-an-issue
### Screenshots
