What problem would this solve?
Sometimes issues are created in the wrong place. This can be frustrating, especially when Gitea's project management features are used extensively. Indeed, depending on where projects, labels, teams, or milestones are located (e.g., in a different repository or organization), it may be impossible to properly assign or categorize a misplaced issue. While it is possible to create an issue "linked" to an existing one using "Reference in New Issue", there is currently no way to directly move an existing issue from one repository to another.
What do you propose?
This proposal suggests adding a built-in "Move/Migrate Issue" option (similar to the pin, lock, and delete buttons in the sidebar) to quickly transfer issues between repositories within the same Gitea instance, avoiding duplicates while preserving their metadata.
What problem would this solve?
Sometimes issues are created in the wrong place. This can be frustrating, especially when Gitea's project management features are used extensively. Indeed, depending on where projects, labels, teams, or milestones are located (e.g., in a different repository or organization), it may be impossible to properly assign or categorize a misplaced issue. While it is possible to create an issue "linked" to an existing one using "Reference in New Issue", there is currently no way to directly move an existing issue from one repository to another.
What do you propose?
This proposal suggests adding a built-in "Move/Migrate Issue" option (similar to the pin, lock, and delete buttons in the sidebar) to quickly transfer issues between repositories within the same Gitea instance, avoiding duplicates while preserving their metadata.