It would be useful to be able to move tickets between different ticket instances. Specific use cases for support would be:
1) moving confirmed bug reports to engr for further eval/processing. So we can maintain separate ticket queues without needing to manage duplicate tickets.
2) moving tickets that should have been logged to a project instead.
I think both these cases could be covered by only allowing users with admin(?) permissions on both tickets instances to move tickets between them.
We should also consider auto-forwarding from the old ticket URL and not re-using the ticket number after a ticket has been moved. Let's not do this yet. But we do need to figure out how to clean up old references to the old artifact path (e.g. solr and artifact references)
Another concern is how to handle custom fields/statuses that aren't shared by both tickets instances. We should just drop those fields/values if they can't be converted. But we should put a comment on the ticket about the conversion and include the full URL of the prior ticket and also insert all the fields/values that couldn't be converted.
The ticket artifact should stay the same, so that subscriptions and other stuff are preserved.
Log in to post a comment.