Custom Fields in Bugzilla
Bugzilla 現在／一般に only has 限られた／立憲的な support for custom fields, and often they are not the 解答 you want anyway. This page gathers together the 選択s you have if you feel the 燃やすing 願望（する） to 追加する extra fields to your 取り付け・設備 of Bugzilla.
選択 0: Do nothing
The first thing to ask yourself is: do you really need this field? Joel Spolsky, a 尊敬（する）・点d ソフトウェア engineer, whose company 令状s a proprietary bug system called FogBugz, has written a 井戸／弁護士席-thought-out piece about why his ソフトウェア will never support custom fields. It points out that several of the 推論する／理由s often given for 追加するing a custom field are 偽の.
選択 1: Turn the feature on
If your mind is made up, then the second question is: does Bugzilla 現実に already support what you want, and you just need to turn the feature on? For example, if you want a field to 追加する an email 演説（する）／住所 to be 通知するd on every bug, enable QA 接触する and use that. If you want fields to 跡をつける what time is spent on each bug, turn on Time 跡をつけるing. Check the "Bug Fields" section of the Parameters.
選択 2: Bug 入ること／参加（者） templates
But if Bugzilla really doesn't 直接／まっすぐに support what you want, then the third question is: do you really want a custom field, or do you just want to 注入する more order and structure into the bug とじ込み／提出するing 過程? Your organisation or 事業／計画（する） may have inexperienced people とじ込み／提出するing bugs, and you think that the default bug とじ込み／提出するing form doesn't 誘発する them for the 権利 （警察などへの）密告，告訴（状）. If that's the 事例／患者, you should 調査／捜査する bug 入ること／参加（者） templates, which were invented to solve just this problem (see the 底（に届く） of the page.) This 許すs you to define 独断的な fields in the bug とじ込み／提出するing page, and put the resulting values into the bug's 初期の comment.
選択 3: Keywords
But, a disadvantage of bug 入ること／参加（者） templates is that you can't easily search on the contents of the new "field", short of doing a 十分な text search of the comments. いつかs you want to label bugs in a way which is more easily searchable. One 選択 here is to use keywords. Bugzilla's keyword system 許すs you to define a 始める，決める of textual tags, such as "dataloss" or "衝突，墜落" and tag any number of bugs with them. For some sorts of data, which perhaps don't 適用する to every bug, these make more sense than a custom field.
選択 4: 旗s
旗s are a bit like a keyword which can have an associated 明言する／公表する, and かもしれない a person. So a "review" 旗 can have 明言する／公表するs + (認可するd), - (拒絶する／低下するd) and ? (requested), in which 事例／患者 it could also have someone the review was requested from. See the 手動式の for more 詳細（に述べる）s. These are a good 代用品，人 for custom 事業／計画（する） 管理／経営 fields.
選択 5: Co-選ぶ an 存在するing field
If keywords don't 削減（する） it, then you have the 選択 of co-選ぶing an 存在するing field which you are not using. If you want freeform text, you can co-選ぶ (and edit the templates to relabel) either the URL field or the Status Whiteboard field. If you want a 選び出す／独身-select from a 名簿（に載せる）／表（にあげる） of 選択s, you can co-選ぶ 優先, Severity, 壇・綱領・公約 or OS. For those four, you define the 始める，決める of possible values on the "Field Values" configuration page. If you want an email 演説（する）／住所, turn on QA 接触する. If you want 多重の email 演説（する）／住所s, make a mailing 名簿（に載せる）／表（にあげる） the QA 接触する.
選択 6: Use the 限られた／立憲的な custom field support
This is 利用できる in Bugzilla 3.0 and above. You can 追加する custom fields which are either freeform text or one-from-many 選択s. See the documentation on the Bugzilla website.