If it's not clear, it will take a list of dictionaries for ticket
changes. The dictionaries look like this:
'ticket_change': [{'author': u'jamie',
                    'field': u'component',
                    'newvalue': u'something',
                    'oldvalue': u'general',
                    'time': 1131496921},
                   {'author': u'jamie',
                    'field': u'status',
                    'newvalue': u'assigned',
                    'oldvalue': u'new',
                    'time': 1131591197},
                   {'author': u'chris',
                    'field': u'status',
                    'newvalue': u'closed',
                    'oldvalue': u'assigned',
                    'time': 1135038571},
                   {'author': u'chris',
                    'field': u'resolution',
                    'newvalue': u'invalid',
                    'oldvalue': u'',
                    'time': 1135038571},
                   {'author': u'chris',
                    'field': u'comment',
                    'newvalue': u"Doesn't matter anymore...",
                    'oldvalue': u'',
                    'time': 1135038571}],


On Tue, Jun 24, 2008 at 2:57 PM,  <[EMAIL PROTECTED]> wrote:
>
> On Jun 24, 11:35 am, "Chris Mulligan" <[EMAIL PROTECTED]>
> wrote:
>> I used the little wrapper I wrote around Trac that I used in my
>> tracmerge script (the code of which is also online, but without
>> documentation).  You'll need ptrac.py, but all it does is implement a
>> database insert command for you.
>>
>> Check outhttp://trac-hacks.org/browser/tracmergescript/yoheeb
>>
> awesome, I was in process of writing something atm so I could dump my
> tickets database and figure out the field order (I wasn't sure how
> trac merged the ticket_custom table in exactly.  As it turns out, my
> sql skills have bit rot and I was getting frustrated (I could NOT dump
> the field names, I just dumped a ticket and mapped the entries to the
> fields on a scrap of paper)
>
> Thanks!  I now have to go play with it so I can learn from it.  My
> next endeavor, will possibly, to try and attach comments/change
> status, as some of these in "the list format" are closed with
> resolution comments.  That said, for this exercise, just getting the
> numbers to match, then going in and  editing the information in trac
> is sufficient as the list is rather small, and the other members need
> a "intro" to trac exercise anyway :D
>
> Man, this group of users rock.  I just hope I can contribute as much
> as I have taken from in the near future here!
> >
>

--~--~---------~--~----~------------~-------~--~----~
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@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to