Hi Erik, > It includes > a UI for designing different "ticket types" from scratch. There's > also an API for adding custom field types, and for adding custom > "Enums" similar to Version and Component. > This, and what you describe later sounds very good to me. What a pitty that you can't share your work. Hopefully your company will change their mind.
I really think something along these lines should be the basic foundation in trac. If this is the case, a lot of plugins can build ontop of the core and does not need to restrict the core, e.g. to hide fields or do some other magic. Again and again, I'm not a python developer, I'm only a user of trac, expressing my needs to extend trac into various fields in our company. Even if I could learn the necessary stuff, my time is filled up with other work and family, so that there is no space left to code for trac. If necessary I could spend some money for someone doing the work. Additionally trac is suiteable to our process, even if it is missing the discussed features. I only expressed my thoughts, that come up every time I play with the trac configuration. If it is benefitial for the developers, I don't know. But it is good to see, that I'm not the only one having this idea. So please try to convince your company about open source and show your enhancements to the trac dev team. I would love to see this included into the core trac. Best regards and thank you for your post Dirk --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
