---
title: "Configuring Test Step Custom Fields"
canonical: "https://docs.getxray.app/space/XRAY/301698079/Configuring%20Test%20Step%20Custom%20Fields"
format: markdown
---
Xray allows Project Managers to configure fields to be available in Manual Test Steps

> Macro (toc)

## Configuration

## Native fields

**Action**, **Data**, and **Expected** Result fields are native fields, i.e, they are present by default. Data and Expected Result can be disabled.


### Actions available

Native fields can be:

- enabled
- disabled
- set as required

![image](media://aa49b4d3-2591-4dce-9ec2-0cfb341106b0)

## Custom fields

### Create

A project manager can create custom fields to be available when designing Manual Tests

![image](media://bf76e9ba-5034-4079-bd6b-bd09e57a8dfa)

### Type of fields Available

Available** **** ****step fields**:

- Toggle
- Date Picker
- Date Picker
- Number field
- Radio button
- Select lists (single choice and multi choices)
- Text field (single and multi-line)
- User Picker

### Actions available

Custom fields can be:

- enabled
- disabled
- set as required
- deleted

![image](media://43802db6-02df-41e4-ba45-18465746384a)

## Limit of Fields

Xray allows up to 6 fields enabled for a step. The Action field is always present and cannot be disabled. All others fields can be disabled and or delete.

## Impact of configuration changes on Tests

Configuration changes made on Test Steps Custom Fields or Native Fields (Data & Expected Result) will be reflected on Tests history, but <u>only for tests that have values for that fields in their Test Steps</u>. The following actions are the ones that are reflected in history:

- **Delete/Remove field:** all affected Tests' history will reflect the deletion of the field;
- **Disable field:** all affected Tests' history will reflect the disable of the field;
- **Enable field:** all affected Tests' history will reflect the return of this field.

> Macro (inline-media-image)

> Macro (inline-media-image)

> Macro (inline-media-image)




Note: Toggle fields - Since the default value for them represents "FALSE", the actions performed in this field will only be reflected in Test History if the value is "TRUE". As you can you see in the example above.

## Impact of configuration changes on existing executions of Tests

Please be aware that a change on a custom field that is being used in a Test already being executed may request an action to reset or merge the test definition: [Updating the definition of the Test after execution started](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/160170368)