Defect #8735
closedMigration, Multiple Trac Instances - Obsolete Ticket References
0%
Description
Hi,
I am migrating several Trac projects to redmine as described here: http://www.redmine.org/projects/redmine/wiki/RedmineMigrate
The guide tells that you require a clean Redmine. But on the other hand side, there are tickets suggesting otherwise:
http://www.redmine.org/issues/595
http://www.redmine.org/issues/2150
So I tried migrating and it seemed to work. Recently the problem came up that the references in comments and descriptions are not updated, even though they need to differ. This difference is caused by Redmine's unique numbers for all issues, independent of the project. In contrast to Redmine, Trac has a project specific ticket enumeration, where the first ticket of every project starts with 1. Consequently, if two Trac instances are migrated to Redmine, and there are references to ticket 1 in the last migrated instance, this will reference the first projects first ticket.
To solve this issue I am currently writing a script to update every comment and description of one project to increase the ticket references they contain by a certain offset.
In the process I encountered the problem that I cannot find a link of an issue belonging to a certain project to the comment in the changesets table. This is due to the fact that the table changesets_issues, responsible for this relation, is empty.
How can I figure out from the database which changesets.comments record belongs to the corresponding issues.project_id ?
http://www.redmine.org/projects/redmine/wiki/DatabaseModel
seems outdated, could you provide a link to the current one? I did not find it by browsing the repository.
Redmine runs with psql-Version 8.4, Serverversion 9.0.
Thanks
Updated by Etienne Massip almost 14 years ago
- Status changed from New to Closed
- Resolution set to Invalid
Closed as this is not an issue, please ask your question in forum.
BTW, changesets are linked via the changesets_issues
table to issues which are linked to projects.