Implementation: We should index ticket's
import_id in solr (put it in the
index() method) so it is searchable. Also make URLs like /myproject/tickets/N when a regular ticket isn't found then fall back to check import_id. If a ticket is found by import_id, do a permanent redirect to the real url for that ticket.
Issue numbers from the sourceforge bug tracking system prior to migration did not migrate in project upgrade, and description of upgrade consequences did not warn of this.
As a test of the project upgrade path, I upgraded the sarmanager project. The consequences of upgrade appear to be poorly documented in the requests for projects to upgrade. One severe side consequence is the renumbering of issues in the sourceforge issue tracking system.
For example, what was issue: 3484452 has become issue 21, breaking crossreferences between the issue tracker and svn commit messages. Thus the commit message in https://sourceforge.net/p/sarmanager/code/35/ can no longer be related to the relevant issue: https://sourceforge.net/p/sarmanager/bugs/21/
A requirement of the migration of an issue tracking system which exposes issue numbers is the retention of issue numbers. Issue numbers may be referenced in many arbitrary places outside of the issue tracking system itself.
I'm not going to be able to upgrade other projects until this issue has been resolved.
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.
I think it's fine that we don't use the same IDs exactly, but we should definitely provide a reference to them.
In the meantime though, since we have redirects in place, using the following link format will let users use discover the corresponding ticket using just the ticket ID:
eg. for sarmanager above: 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)