export script (bugzilla, Mantis, perforce, etc.)

68 views
Skip to first unread message

yoheeb

unread,
Nov 6, 2009, 3:56:00 PM11/6/09
to Trac Users
Hi all,

can someone point me to scripts to export FROM Trac and then import
into other systems? All our work is getting transferred and I need to
know, what, if any, other systems I can easily export for them, and
which ones will import best, etc.

Mantis and perforce are probably on the top of the list.

Thanks

yoheeb

unread,
Nov 6, 2009, 4:21:39 PM11/6/09
to Trac Users
Forgot to mention, would be ideal if I could get attachments and
include a reference to them in some part of the export/import process.

Cooke, Mark

unread,
Nov 9, 2009, 4:33:41 AM11/9/09
to trac-...@googlegroups.com
>
> Hi all,
>
Hello,

> can someone point me to scripts to export FROM Trac and then import
> into other systems? All our work is getting transferred and I need to
> know, what, if any, other systems I can easily export for them, and
> which ones will import best, etc.
>

This list generally is interested in moving _from_ other systems _to_
Trac, so are unlikely to invest much (any!) effort in going the other
way. What you probably need to do is look at your candidates (Mantis
and perforce) and see if _they_ provide suitable scripts (Trac has
bugzilla2trac.py for example)

Cheers...

yoheeb

unread,
Nov 23, 2009, 10:37:06 AM11/23/09
to Trac Users
yep, already done that. No luck. I realize the list probably doesn't
care much, heck, I don't care much about it, since I am not part of
the "move", it's really someone else's problem, but I thought I would
be nice and try to see if anyone has done this.

I think the easiest way will be a 2 part process. First, just export
the tickets to csv, including change history. Then a second pass to
extract attachements from each ticket, and put in a identifiable
location. Then, whatever their system is, they care reverse the
process for import, tracking their start number and offsetting for
attaching the attachments. I personally am a bigger fan of just
printing them out and shoving in a binder. They can create new
tickets going forward, and any outstanding ones can be created
manually.
Reply all
Reply to author
Forward
0 new messages