Noah Kantrowitz kirjoitti:
>> -----Original Message-----
>> From: [email protected] [mailto:[EMAIL PROTECTED]
>> On Behalf Of Jani Tiainen
>> Sent: Friday, October 31, 2008 1:34 PM
>> To: [email protected]
>> Subject: [Trac] Plugin provided custom field
>>
>>
>> What would be needed for making plugin to populate ticket fields by
>> code?
>>
>> I would like to do something like:
>>
>> myfield = customer-selector
>> myfield.label = Customer
>>
>> I found at least two related tickets 5641 and 4549 which both are
>> referring partially what I'm trying to do.
>>
>> I also found that ITicketManipulator has method "prepare_ticket", which
>> of course reads "Not currently called, but should be provided for
>> future
>> compatibility."
>>
>> Specially ticket 5641 has something that "could be done as a plugin"
>> but
>> no further reference. So, how it can be done?
>>
>
> Make a request filter that puts whatever you want in the options member of
> the field (in the data dict directly).
Works otherwise pretty well, BUT for some reason fields in ticket and
fields in queries are of course in a marginally different format.
In ticket data fields are in form {name: 'nameoffield', default : ''
},{name : 'name of other field', default : ''} and in query
{'nameoffield' : {default : ''}, 'name of other field' : {default : ''}}
Couldn't figure out rationale behind this behavior. It just makes filter
method a bit more complex but nothing major.
--
Jani Tiainen
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
