You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@bloodhound.apache.org by Patrick West <we...@rpi.edu> on 2015/02/16 05:05:05 UTC

migrating old trac tickets to bloodhound

I have about 225 tickets in our new bloodhound installation.

I’ve been able to rescue the old trac database from a server that had crashed.

And now I want to migrate all the old trac tickets into our new bloodhound installation.

But I’m not finding a way to do this.

I tried an old python script that migrates tickets from one trac to another, and it looks like the tickets are in the new db, but I don't see them anywhere in the GUI. I defaulted all the products to DEF.

Any help would be greatly appreciated.

Thanks,


Re: migrating old trac tickets to bloodhound

Posted by Patrick West <we...@rpi.edu>.
On Feb 16, 2015, at 12:32 PM, Ryan J Ollos <rj...@apache.org> wrote:

> On Sun, Feb 15, 2015 at 10:36 PM, Patrick West <we...@rpi.edu> wrote:
> The script, it seems, is incomplete. It only takes the attachments table and ticket_change table and migrates them from one .db file to the other, creating entries in the ticket table as it goes. It creates new ticket numbers as it goes, I think. That’s what it looks like, at least.
> 
> Oh, and we’re using sqlite3. And I found this script online, didn’t write it all.
> 
> Attached is the script.
> 
> To get it to work I had to add a column to the attachment and ticket_change tables to account for the product, defaulting to the Default product.
> 
> Seems the information is in the database, but the tickets don’t show up in the UI.
> 
> Patrick
> 
> It should be the aim of the Bloodhound project to distribute a migrate-from-trac script in the source, perhaps in a contrib directory. There was some discussion early on about a migrate-from-jira script, but not sure if anything every came of that.
> 
> Where did you find the script?

Actually … I didn’t bookmark it, so I don’t remember. It seems close, but must be missing something since I can’t see the tickets. They appear in the database, but not in the GUI.

> 
> - Ryan


Re: migrating old trac tickets to bloodhound

Posted by Ryan J Ollos <rj...@apache.org>.
On Sun, Feb 15, 2015 at 10:36 PM, Patrick West <we...@rpi.edu> wrote:

> The script, it seems, is incomplete. It only takes the attachments table
> and ticket_change table and migrates them from one .db file to the other,
> creating entries in the ticket table as it goes. It creates new ticket
> numbers as it goes, I think. That’s what it looks like, at least.
>
> Oh, and we’re using sqlite3. And I found this script online, didn’t write
> it all.
>
> Attached is the script.
>
> To get it to work I had to add a column to the attachment and
> ticket_change tables to account for the product, defaulting to the Default
> product.
>
> Seems the information is in the database, but the tickets don’t show up in
> the UI.
>
> Patrick
>

It should be the aim of the Bloodhound project to distribute a
migrate-from-trac script in the source, perhaps in a contrib directory.
There was some discussion early on about a migrate-from-jira script, but
not sure if anything every came of that.

Where did you find the script?

- Ryan

Re: migrating old trac tickets to bloodhound

Posted by Patrick West <we...@rpi.edu>.
The script, it seems, is incomplete. It only takes the attachments table and ticket_change table and migrates them from one .db file to the other, creating entries in the ticket table as it goes. It creates new ticket numbers as it goes, I think. That’s what it looks like, at least.

Oh, and we’re using sqlite3. And I found this script online, didn’t write it all.

Attached is the script.

To get it to work I had to add a column to the attachment and ticket_change tables to account for the product, defaulting to the Default product.

Seems the information is in the database, but the tickets don’t show up in the UI.

Patrick


Re: migrating old trac tickets to bloodhound

Posted by Olemis Lang <ol...@gmail.com>.
On 2/15/15, Patrick West <we...@rpi.edu> wrote:
> I have about 225 tickets in our new bloodhound installation.
>
> I've been able to rescue the old trac database from a server that had
> crashed.
>
> And now I want to migrate all the old trac tickets into our new bloodhound
> installation.
>
> But I'm not finding a way to do this.
>
> I tried an old python script that migrates tickets from one trac to another,
> and it looks like the tickets are in the new db, but I don't see them
> anywhere in the GUI. I defaulted all the products to DEF.
>

What does the script do ? Could you please provide more details about
what you did ?

-- 
Regards,

Olemis - @olemislc

Apache(tm) Bloodhound contributor
http://issues.apache.org/bloodhound
http://blood-hound.net

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article: