#6100 URL-Redirection for moved tickets - NEEDS ENSURE_INDEX

v1.0.1
closed
nobody
support (446) p3 (267) 42cc (432)
Tracker
Tim Van Steenburgh
2015-08-20
2013-04-11
Anonymous
No

Originally created by: vampire0

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.

Related

Tickets: #6100
Tickets: #6665

Discussion

  • Chris Tsai - 2013-08-14
    • labels: --> support, p3
    • Component: General --> Tracker
    • Milestone: limbo --> forge-backlog
     

  • Dave Brondsema

    Dave Brondsema - 2013-08-22
    • labels: support, p3 --> support, p3, 42cc
     

  • Dave Brondsema

    Dave Brondsema - 2013-08-22

    Of course, needs to work with both bulk move and individual move

     

  • Anton Kasyanov - 2013-08-23

    Created #420 [#6100] URL-Redirection for moved tickets

     

    Related

    Tickets: #6100

  • Anton Kasyanov - 2013-08-23
    • status: open --> in-progress
     

  • Igor Bondarenko - 2013-09-03
    • status: in-progress --> code-review
     

  • Igor Bondarenko - 2013-09-03

    Closed #420. je/42cc_6100

     

  • Anonymous - 2013-09-03

    Originally by: vampire0

    Just as a side-note, it should probably also work through multiple moves. :-)

     

  • Tim Van Steenburgh - 2013-09-03
    • QA: Tim Van Steenburgh
    • Milestone: forge-backlog --> forge-sep-06
     

  • Tim Van Steenburgh - 2013-09-04
    • status: code-review --> in-progress
    • QA: Tim Van Steenburgh --> nobody
     

  • Tim Van Steenburgh - 2013-09-04

    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.

     

  • Igor Bondarenko - 2013-09-05

    Created #431: [#6100] URL-Redirection for moved tickets followup (3cp)

     

    Related

    Tickets: #6100

  • Dave Brondsema

    Dave Brondsema - 2013-09-06
    • Milestone: forge-sep-06 --> forge-sep-20
     

  • Igor Bondarenko - 2013-09-13
    • status: in-progress --> code-review
     

  • Igor Bondarenko - 2013-09-13

    Closed #431. Branch je/42cc_6100

     

  • Tim Van Steenburgh - 2013-09-17
    • QA: Tim Van Steenburgh
     

  • Tim Van Steenburgh - 2013-09-18
    • summary: URL-Redirection for moved tickets --> URL-Redirection for moved tickets - NEEDS ENSURE_INDEX
    • status: code-review --> closed
     

  • Tim Van Steenburgh - 2013-09-18

    Very nice!

     

Log in to post a comment.