Hello Dalton, thanks for your answer.
Using custom fields is in my opinion not the correct way what i'm now trying to explain. I have/create a new Ticket, This ticket should split amount work in separated working packages. So i will have for example the following structure: Ticket #xy -ticket fields -custom fields -budgeting Fields Budgeting Fields are Person Typ Estimation Cost Status Comment It is possible to add n (typically 5-10 Rows) to a single ticket to build as example the following structure Mike Test 10.0 5.0 done Blackbox test Ann Development 45.5 40.0 working implementing new features Vic Specification 12.0 12.0 done define the new feature functionality .... and so on So in this case, i will have 18 new custom fields, an as i said this will for normal more. Adding all this fields by custom_fields isn't in my opinion a nice way to store all this extra information and secondery i will blow up the config.ini. All of this reasons i decided to implement a new table BudgetingTable an keeping all my extra information in this. Using custom fields is much more easier, i know. But in this case it isn't benefical. For the moment i'm searching for an chance to accessing my fields to may check it by jquery an after all to store it to my table. For make my self clear, i added a screenshot of the part, with i had developed greeting -- 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.
