yoheeb at gmail
Nov 23, 2009, 7:37 AM
Post #4 of 4
(6 views)
Permalink
|
|
Re: export script (bugzilla, Mantis, perforce, etc.)
[In reply to]
|
|
On Nov 9, 3:33 am, "Cooke, Mark" <mark.co...@siemens.com> wrote:
> > 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...
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.
--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users[at]googlegroups.com.
To unsubscribe from this group, send email to trac-users+unsubscribe[at]googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-users?hl=.
|
