Noah Kantrowitz kirjoitti: > On Nov 9, 2008, at 2:40 AM, Jani Tiainen wrote: > >> What would be required for following things that they could be done >> from >> plugin: >> >> >> - Custom new fieldtypes to tickets or creating ticket fieldtypes on >> the >> fly from the plugin. It's very annoying that if you install some >> plugin >> that needs custom fields on ticket you need to _manually_ add fields >> that are _required_. > > This is already possible, check the 'fields' object in the data dict.
Well I've already one plugin that plays around with that. Only minor thing is that content of "fields" object is not consistent betweem ticket and ticket query API. Is there simple way to intercept field creation to create different field(s)? For example I would like to have type "list" that you can select one or more options. >> >> - Populating user session data from other source than trac database. >> LDAP for example. > > IUserDirectoryProvider. There are a number of tickets and some patches > floating arounds Any favourite patches? That one came up in my mind too but IIRC it's planned for 0.13 which at current pace takes few years to come.. :) >> >> - Ticket relations, (I know MasterTicketPluing creates simple >> relation) >> but I'm referring to more project management relatiobs like start to >> start, end to start and end to end. > > If you are looking for more than mastertickets providers, you will > need to be more specific. Well like I wrote, like gantt-type relations, in conjunction with some datefields (start, end), workflow that contains "in work" relations like "end to start" so I could do something like: Ticket #1 relates to ticket #2 type end to start. So ticket #2 state cannot change state until ticket #1 is closed. Also sometimes I've been (not very frequently but sometimes) in need for having real parent-child relations so I could hide either parent or children... -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
