Redmine

Overview¶

It would be useful to have a feature that allows an existing repository to be moved from one project to another without deleting and re-registering it.

Currently, when a repository needs to be assigned to a different project, the usual approach is to delete it from the original project and register it again in the destination project.

However, deleting a repository also deletes its associated changesets and related data, including the associations between changesets and issues. As a result, links between issues and their related revisions are lost.

Proposed behavior¶

Add an operation to move an existing repository to another project.

The operation should change the repository's project association while preserving its existing data, including:

• Changesets
• File changes
• Changeset-to-issue associations
• Changeset parent relationships

The repository itself should retain its identity, and existing changesets should not need to be re-imported.

Use cases¶

This feature would be particularly useful when:

• Splitting or reorganizing projects
• Transferring repository ownership between projects
• Consolidating or restructuring project hierarchies

Benefits¶

This would make repository management safer and more convenient, especially when reorganizing projects, while preserving the integrity of existing issue and revision history.