This repository has been archived by the owner on May 11, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Script to assist in migrating existing Request Tracker (tm) systems to Redmine (tm) systems
License
jsr6720/Request-Tracker-to-Redmine-Migration
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
== Author's Note This was the first "open source" contribution I had ever made. I was so proud that I had made something that might help someone else. Archiving roughly 13 years later. :single-tear-emojii: == Introduction This project was meant for transitioning from an RT based tracking system to Redmine. This script was tested with RT 3.8.4 and Redmine 1.0.4 == WARNING This script was created as a bare minimum to get a targeted RT installation to a redmine instance. Not all features are supported, or converted properly. It would seem the entire migration could be done via the transaction table instead of 'mapping' things, but that's a project for another day. == Usage OPTIONAL: https://github.com/jystewart/html2textile for converting html text to textile. download and install otherwise RT plaintext is migrated. Copy migrate_from_rt3.rake into the {redmine}/lib/tasks directory (with the other rake tasks). execute $rake redmine:migrate_from_rt3 RAILS_ENV={production/development/test} == LICENSE Licensed using the MIT (http://www.opensource.org/licenses/mit-license.php) Read: I don't care what you do, I just don't want to be liable for anything. == Targets for migrating Roughly: RT3 Redmine Custom Fields => Issue Custom Fields Tickets => Issues Queues => Projects (or attributes of projects) Users => Users Groups => Groups
About
Script to assist in migrating existing Request Tracker (tm) systems to Redmine (tm) systems