Earlier in this book, we learned how to create custom fields. The purpose of these fields is to store some additional information that is otherwise not possible with default system fields in Jira.
Too many custom fields is the biggest reason for slow performance in Jira. There really is no reason to have hundreds of custom fields in Jira and caution should be exercised when creating a new custom field. Just as with statuses, try to reuse a custom field and also try to create custom fields with generic names.
Let's take a look at some generic custom fields that can be created in Jira instances:
|
Custom field |
Type |
Description |
|
Client/customer |
Select List |
This uses Project Context to create different options for multiple projects |
|
Category |
Select List |
Labels and components should be used in most cases, but this generic... |
