Hi, I tried this method, and does work ( a bit). Now I can not figure out why I can not insert values into ticket_custom table. Values go fine into ticket table and do appear fine in browser but nothing gets inserted into ticket_custom. I do not get any error or any warning when I insert into ticket_custom, but the data gets lost, and nothing appears. any idea whats going on ? Regards
On Oct 2, 10:20 pm, "Erik Bray" <[EMAIL PROTECTED]> wrote: > On Thu, Oct 2, 2008 at 4:26 PM, [EMAIL PROTECTED] > > > > > > <[EMAIL PROTECTED]> wrote: > > > Hi please pardon me for any ignorance, as this is my first encounter > > with trac and on this mailing list. > > Now back to business. > > I have to move data from existing legacy bugtracking system, (which is > > Microsoft Access based and contains more than 100,000 tickets), to > > trac 0.11 + sqlite3. Now after looking at all the schemas in MS > > Access, I have created a small application, which will go through > > existing tickets and views one by one in access db and insert records > > into trac 'ticket' and trac 'ticket_custom' tables. Now question is, > > am I doing it the right way, or missing some thing. > > Another question arises is that the priority in legacy Ms Access db is > > 'High,Normal,Low'. So I want to change the trac's priority drop down > > values to ones in access db. I tried something like this in trac.ini > > where there are default values for priority (please ignore typo for > > priority) > > default_priority = 'low' > > default_priority.options = High|NormalLow > > but this didnt work. > > Although I changed some bits in components table, and can have my own > > component and mile stone values. > > > Any idea if you see problem with my approach to migration, please ring > > the bell. > > Any help will be appreciated. > > Regards > > Your approach for migrating the tickets themselves sounds just fine. > I don't know if you're trying to also import ticket histories, but > that's what the ticket_change table is for. Otherwise, I suppose your > tickets will just be treated like new tickets, and any changes after > the move to Trac will be recorded accordingly. > > As for priorities the way you were trying to do it won't work at all. > The default_priority option only sets the default value for the > priority field in a ticket. It's not a custom field, and its options > aren't set that way. You can edit the priorities through Trac's admin > interface. Look under the Ticket section of the admin interface and > select Priority.- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
