#637 Keeping tracker ID when migration to the new (beta) project

fixed
2012-11-15
2012-09-18
No

I'm wondering if it is possible to keep the old tracker ID of issues in the bug/feature request/... tracker in a classic project, when migrating to the new (beta) project?

One of my projects uses the tracker ID's to link to bugs or feature requests from the release notes/changelog. When migrating to the new project, all tracker items would get a new ID. So it would be useful to have either/both :
- a redirect in place that redirects to the ticket in the new project when requesting the tracker item in the classic project.
- get a list of tracker items with the old ID and the new ID. This way, our current references to tracker items could be converted to reference the new tracker ID's.

Related

Apache Allura: Tickets: #5184

Discussion

  • Anonymous - 2012-09-18

    Greetings,

    This is certainly an important item to have reference to, I'm escalating this to our engineering team here: [allura:tickets:#4968]

    That said though:

    • a redirect in place that redirects to the ticket in the new project when requesting the tracker item in the classic project.

    That is already in place, so, if you use the following url format, you can use that to discover the corresponding ticket using just the original ticket ID: https://sourceforge.net/support/tracker.php?aid=1234567

    eg. using an example from [#623], https://sourceforge.net/support/tracker.php?aid=3484452 will redirect to https://sourceforge.net/p/sarmanager/bugs/21/ (technically, there's actually an intermediate redirect as well)

    Regards,
    Chris Tsai, SourceForge.net Support

     

    Related

    Site Support: #623

  • Anonymous - 2012-09-18
    • labels: --> engr, nf-4968, forge, p3
    • status: unread --> assigned
    • assigned_to: Chris Tsai
     
  • Anonymous - 2012-10-24
    • labels: engr, nf-4968, forge, p3 --> engr, nf-5184
     
  • Anonymous - 2012-10-24

    Okay, the changes are live for [allura:tickets:#4968], but neither the new nor old redirects are working for your project, so I'm re-raising this to our engineering team here: [allura:tickets:#5184]

    Thanks,
    Chris Tsai, SourceForge.net Support

     

    Related

    Apache Allura: Tickets: #5184


    Last edit: Anonymous 2012-10-24
  • Anonymous - 2012-11-07
    • status: assigned --> pending
     
  • Anonymous - 2012-11-15
    • status: pending --> fixed
     
  • Anonymous - 2012-11-15

    We haven't heard from you in a while. I'm closing this ticket due to inactivity. If you find that the redirect issue mentioned in my latest post is going to be a major issue, please open a new ticket.

    Regards,
    Chris Tsai, SourceForge.net Support

     
  • Dieter Adriaenssens

    Thanks for fixing the bug. I seem to have missed your message of 2012-11-7.
    The mentioned scenario is no issue for me.

    Kind regards,

    Dieter Adriaenssens

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks