> For the complete documentation index, see [llms.txt](https://docs.specsolutions.eu/specsync/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.specsolutions.eu/specsync/jira/features/push-features/customization-setting-test-case-fields-with-default-values.md).

# Customization: Setting Test Case fields with default values

The *Field defaults* customization can be used to initialize arbitrary Test Case fields that are otherwise would not be updated by SpecSync to a default value. This might be useful for custom Jira process templates.

{% hint style="info" %}
The *Field defaults* customization described here is an [Enterprise feature](/specsync/jira/licensing.md).
{% endhint %}

In order to enable this customization, the `customizations/fieldDefaults` section of the configuration has to be enabled. The complete reference of the configuration settings can be found in the [customizations configuration reference](/specsync/jira/reference/configuration/configuration-customizations.md#fielddefaults).

The following example shows a basic configuration that initializes the field `MyCompany.MyCustomField` to `value1`.

```javascript
{
  ...
 "customizations": {
    "fieldDefaults": {
      "enabled": true,
      "defaultValues": {
        "MyCompany.MyCustomField": "value1"
      }
    }
  }
  ...
}
```

This customization uses the specified values only to \_initialize \_the field when the Test Case is created. To update custom fields, use the [*Custom field updates* customization](/specsync/jira/features/push-features/customization-update-custom-test-case-fields-on-push.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.specsolutions.eu/specsync/jira/features/push-features/customization-setting-test-case-fields-with-default-values.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.