On Jan 29, 2:11 pm, Vishal <[email protected]> wrote: > I would like to use TRAC in one of my projects as a project management > system. > In that sense, there is a need to create multiple custom fields for > tickets. As I saw in the docs, this is possible by editing the > trac.ini, which i did and could see the corresponding changes. > However, the option list for some of these fields could be "very" long > and option names may be really big. Hence. I am looking for a way of > not using the INI and instead send all this data to the trac.db. > > Interestingly, on polling trac.db, using sqlite command line > interface, none of these options actually end up in the > database...they are solely in the INI. > > is there a way to avoid this and send all this data to trac.db? > > Any pointers would be highly apprecaited.
Nope, no way around that the way ticket fields currently works. Custom fields don't become part of the database model, they just get registered on tickets and as changes. I can (shamelessly) recommend my plugin that makes administration slightly easier, and that mimics the way other Ticket meta-information in Trac can be configured by project/ticket administrators - it provides a webadmin interface to the trac.ini changes: http://trac-hacks.org/wiki/CustomFieldAdminPlugin :::simon https://www.coderesort.com http://www.ohloh.net/accounts/osimons -- 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.
