What does this feature do?
On sites where there are many similarly-related projects, but large enough in scope as not to make sense to be "components" of a larger project, users may sometimes create a ticket under an incorrect project.
As all tickets are stored in a single table, allowing the Manager of Project A to move a ticket to related Project B would be a nice new feature.
What makes this feature interesting?
Unless I am missing something, nothing like this currently exists.
In the case where incorrectly placed tickets are generated, we are currently closing them as invalid placement and opening a new ticket under the appropriate project.
Removing this step by adding the feature described above would help to improve the ticket management process.