<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>At our location such wishes had the effect that we renamed<br>
Product -> Team<br>
Component -> Component<br>
Version -> Project<br>
Milestone -> Iteration<br>
Severity -> Task Type<br>
Platform -> PM Type<br>
OS -> Dev Type<br>
<br>
</tt>Since these are terms which are hardcoded almost anywhere, we had
quite<br>
a lot to change in almost any file.<br>
<br>
Customisation of such definitions in a central place would have helped
us<br>
enourmosly.<br>
<br>
Best regards,<br>
Andreas<br>
<br>
Joel Peshkin wrote:
<blockquote cite="mid419CB888.8090406@peshkin.net" type="cite">
<meta http-equiv="Context-Type"
content="text/html; charset=iso-8859-1">
<title>Re: Feature Request: More customizable terms</title>
<p> Dave Williss wrote: </p>
<p> > I'd like to be able to customize more of the terms shown in
Bugzilla. <br>
> Specifically, we'd like to be able to have "enhancement" show up
as <br>
> NFR (New Feature Request) without changing how it's actually
stored <br>
> and having to change every place where it's referenced in the CGI <br>
> scripts. The term NFR, besides being what our staff is used to <br>
> calling them, fits better on the bug lists. </p>
<p> All you have to do is edit localconfig and rerun checksetup. </p>
<p> - <br>
To view or change your list settings, click here: <br>
<<a
href="http://bugzilla.org/cgi-bin/mj_wwwusr?user=andreas.hoefler@bearingpoint.com">http://bugzilla.org/cgi-bin/mj_wwwusr?user=andreas.hoefler@bearingpoint.com</a>>
</p>
</blockquote>
<br>
<pre class="moz-signature" cols="200">--
Reclaim Your Inbox!
<a class="moz-txt-link-freetext" href="http://www.mozilla.org/products/thunderbird">http://www.mozilla.org/products/thunderbird</a></pre>
</body>
</html>