<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=koi8-r">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">
<TITLE>RE: Custom Fields again</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Good $daytime,</FONT>
</P>
<P><FONT SIZE=2>> From: Bradley Baetz [<A HREF="mailto:bbaetz@student.usyd.edu.au">mailto:bbaetz@student.usyd.edu.au</A>]</FONT>
<BR><FONT SIZE=2>> Sent: Wednesday, December 11, 2002 6:19 PM</FONT>
<BR><FONT SIZE=2>> To: developers@bugzilla.org</FONT>
<BR><FONT SIZE=2>> Subject: Re: Custom Fields again</FONT>
</P>
<P><FONT SIZE=2>> > Adding a custom field is either an initial</FONT>
<BR><FONT SIZE=2>> > configuration thing or it's a Big Deal to add when you do it. </FONT>
</P>
<P><FONT SIZE=2>> Why is it a Big Deal? Or rather, why should it be a Big Deal?</FONT>
</P>
<P><FONT SIZE=2>Because we don't want custom fields to be 'cheap'. Instead we </FONT>
<BR><FONT SIZE=2>encourage administrator to think well before doing that.</FONT>
</P>
<P><FONT SIZE=2>And yes, if custom fields reconfiguration would require me to take</FONT>
<BR><FONT SIZE=2>database offline, I'd first look how to implement desired feature</FONT>
<BR><FONT SIZE=2>within standard functionality.</FONT>
</P>
<P> <FONT SIZE=2>Regards,</FONT>
<BR> <FONT SIZE=2>Willy.</FONT>
</P>
<P><FONT SIZE=2>--</FONT>
<BR><FONT SIZE=2>No easy hope or lies | Vitaly "Willy the Pooh" Fedrushkov</FONT>
<BR><FONT SIZE=2>Shall bring us to our goal, | Control Systems and Processes Division</FONT>
<BR><FONT SIZE=2>But iron sacrifice | LUKOIL Company, Chelyabinsk Branch</FONT>
<BR><FONT SIZE=2>Of Body, Will and Soul. | VFedrushkov@LUKoil.com</FONT>
<BR><FONT SIZE=2> R.Kipling | +7 351 262 0367</FONT>
</P>
</BODY>
</HTML>