This works fairly well but doesn't work if a ticket is moved more than once. I discussed with Dave and we came up with the following:
1. Create a new Artifact type called MovedArtifact with fields _id, project_id, app_config_id, moved_to_url 2. Create a MovedTicket subclass with a ticket_num field 3. In the general case, when an artifact is moved, create a MovedArtifact instance "in its place," with ids that match the pre-move artifact (_id, app_config_id, project_id), and set the moved_to_url to the url that the artifact is being moved to. 4. When a ticket is moved, create a new MovedTicket instance, which also sets ticket_num. 5. Now, if ticket is not found, look for a MovedTicket with the same project, app_config, ticket_num, and redirect to the moved_to_url. In this way, multiple moves will also work. Finally - the ticket API needs to be updated to follow these redirects also. --- ** [tickets:#6100] URL-Redirection for moved tickets** **Status:** in-progress **Labels:** support p3 42cc **Created:** Thu Apr 11, 2013 10:50 PM UTC by Björn Kautler **Last Updated:** Tue Sep 03, 2013 09:18 PM UTC **Owner:** nobody As Tickets no longer have a site-wide unique ID which I really find is a pity regarding easy link generation for ticket IDs. And especially now that the ID of a ticket will change if you move it from one ticket tool to the other, this is really bad. Please at least implement a redirection from the old address to the new address if a ticket was moved. --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
