forked from jsr6720/Request-Tracker-to-Redmine-Migration
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
45 lines (27 loc) · 1.44 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
== Changes by github/tdb
The changes I've made in this fork at purely for my own benefit.
They're likely not useful as-is to others, but I'm sharing them
here anyway in case someone wants to cherry pick one out.
Unless your situation is identical to mine this copy of the script
is unlikely to do what you want.
== 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