-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12.01.2013 14:56, rowan.bradley wrote: > Did you ever get a reply to this question? > > I have a similar question - I would ike to change the name "Component" to > "Topic" or "Area" or similar, since I'm trying too use Trac for tickets but > not associated with something that has "components".
The fasted way to implement these ideas is to use custom fields [1]. Standard ticket field won't cease existence in the Trac db, but removing all values will instantly make them disappear from the web-UI. Sure, built-in goodies like assign-ticket-to-component-owner and ultimately everything about such a special (enum) Trac object isn't strait-forward to get for your Topic/Area, but first and foremost you insisted, that Area/Topic should be different. Here you are. Btw. the OP assertion about patching Trac code for renaming the Milestone object will certainly still apply, but we certainly don't care about Clearsilver templates anymore. Beyond Trac 0.11 everything is using Genshi templates. For what it's worth I'm not using Trac for anything related to software development at all. So I've done a lot of customizing by means of configuration and using a bunch of Trac plugins. But I've not found it necessary to rename core ticket fields, nor would I suggest to attempt such action. IMHO there's no big problem to introduce a couple of Trac-specific terms to an organization, if Trac in general is a nice/perfect fit for the requirements. I strongly suggest to focus on customizing the ticket-workflow, wiki front page and make your Trac a great first-time experience by other means as well. I.e. importing historic data from other sources, is a great way to get users interested. Migration as a key factor for acceptance of new systems is generally underestimated, and often dropped in favor of questionable new features. Eventually you'll find yourself in an unexpected situation: Getting feature/enhancement requests without anybody asking about such things as component or milestones, if you don't need them or could give a good alternative explanation for them in your context. Steffen Hoffmann [1] http://trac.edgewall.org/wiki/TracTicketsCustomFields -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDx8ikACgkQ31DJeiZFuHd8hgCgsxfu+XQ6qsRjFpFY0TqWv07P rJcAoKPsdW4qtsie0lNXKBJ2lQDPAHbT =WBS0 -----END PGP SIGNATURE----- -- 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.
