Opened 18 years ago
Closed 8 years ago
#647 closed enhancement (wontfix)
RequestTracker import script
| Reported by: | Wade Brainerd | Owned by: | anybody |
|---|---|---|---|
| Priority: | normal | Component: | Request-a-Hack |
| Severity: | normal | Keywords: | |
| Cc: | Trac Release: | 0.9 |
Description
I know of several organizations using Best Practical RT who would love to switch to Trac.
Is anyone working on an importer script?
Best regards,
Wade Brainerd Technical Director Activision Central Technology
Attachments (2)
Change History (8)
comment:1 Changed 18 years ago by
comment:2 Changed 18 years ago by
I should have signed my comment.
Regards, Sebastian
-- Sebastian Theophil stheophil@… Software Engineer
think-cell Software GmbH Invalidenstr. 34 D-10115 Berlin http://www.think-cell.com
comment:3 Changed 18 years ago by
The script attached assumes that the postgres version of trac is installed.
It is also tuned for our custom fields (status, effort, requestor) but can easily be modified for your own setup of RT.
Execute MySql Script to create a set of Postgres SQL scripts.
Execute output SQL scripts on postgres.
Execute series of postgres commands on postgres.
NB. Depending on your data you may need to drop the primary key on ticket_change whilst migrating.
comment:4 Changed 18 years ago by
In addition you will also need to execute the attached Stored Procedure (requires language plpgsql) to sort an issue with migrated tickets not allowing updates.
comment:5 Changed 15 years ago by
| Summary: | Best Practical RT -> Trac importer → RequestTracker import script |
|---|
comment:6 Changed 8 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
I'm also planning to take a look at Trac because we are not happy with RT. RT is very clumsy and a pain to maintain. We didn't even try to start changing some of its functionality.
I'll probably look into the problems of importing RT stuff to Trac but I don't know when this will be.