Mailing-List: contact user-help@bloodhound.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@bloodhound.apache.org
Received-SPF: pass (athena.apache.org: domain of olemis@gmail.com designates
 209.85.213.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <731C2A51-0002-4557-BFC9-267E435EE7CD@rpi.edu>
References: <731C2A51-0002-4557-BFC9-267E435EE7CD@rpi.edu>
Date: Mon, 16 Feb 2015 00:18:30 -0500
Message-ID: 
 <CAGMZAuNxnjyZ+keqFqMNxVOoKyvmPe0s+Tpgfyx1X3YoyLYWVw@mail.gmail.com>
Subject: Re: migrating old trac tickets to bloodhound
From: Olemis Lang <olemis@gmail.com>
To: user@bloodhound.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 2/15/15, Patrick West <westp@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: