> For the complete documentation index, see [llms.txt](https://bt-studio.gitbook.io/bestest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bt-studio.gitbook.io/bestest/administration/new-custom-fields.md).

# \[NEW] Custom Fields

Add custom fields in the project settings / fields menu for all testing objects:

<figure><img src="/files/6sDVoIppRou2ib3f47eb" alt=""><figcaption></figcaption></figure>

During creation, select **field type**, add **details**, and choose the **placement**(where to show):

* Auto - BesTest arrange them by type (dates, people etc. automatically grouped)
* Main - on the left side, with bigger size
* Custom Fields - after the built-in section, bottom right
* Automation (TC only) - grouped with the Test Automation section

<figure><img src="/files/wGARyj8fcFtMdoovFlbs" alt=""><figcaption></figcaption></figure>

Select and multi-select fields have the option to add colors to the values for better visibility on the UI.

<figure><img src="/files/8qSjC6AQnqVinWtIhFww" alt=""><figcaption></figcaption></figure>

Custom fields appear in the catalog views, can be used in the collection and can be filtered for.

<figure><img src="/files/TBPM4rAtn0WsVnyznIgG" alt=""><figcaption></figcaption></figure>

One of the best usage for custom fields (for test cases), is to build more granular, in-depth collections with them, so that planning a cycle could be straightforward.&#x20;

<figure><img src="/files/bjg0GXGaUCX73WqkL9Ge" alt=""><figcaption></figcaption></figure>

Custom fields are completely supported during import, you only need to create them before import, so that you can map your data with them.

<figure><img src="/files/cDOwo2oJbiJEDrNz4uHm" alt=""><figcaption></figcaption></figure>