---
title: "Using custom fields"
canonical: "https://docs.getxray.app/space/XRAYCLOUD/44567872/Using%20custom%20fields"
format: markdown
---
Xray provides a set of custom fields that can be used for several issue types, as detailed in [Custom Fields and Screen Configuration](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566483).

Aside from these, you can add your own custom fields to these Xray issue types: Tests, Pre-Conditions, Test Sets, Test Executions, Test Plans.

You can't add custom fields to Test Runs because they're not Jira issues.


> Macro (toc)

# Xray-provided custom fields

As mentioned in [Custom Fields and Screen Configuration](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566483), whenever you install Xray, it will also add custom fields that are available <u>only for some issue types</u>. Below are explanations of some of the most important ones:

## Begin Date

The start date for the Test Execution or Test Plan.

## End Date

The end date for the Test Execution or Test Plan.

## Revision

The system revision (or code revision) being tested in the context of a given Test Execution. It is an open field that can contain the Git commit hash or the SVN revision, for example. Some users use it to put the build number/identifier.

# Adding your own custom fields

You may add CFs to Tests; however, they’re not copied to the Test Run. Custom fields in Tests can be seen as complementary, non-relevant information.

Adding custom fields is not limited to the Test issue type; they can also be added to other Xray issue types, including the Test Execution and the Test Plan. For example, you could add a custom field to identify the browser version to the screen of a Test Execution. Note that, in this example, if you want to analyze your Test Execution per browser, it would be preferable to use the **Test Environment** custom field instead; otherwise, you can add some custom fields to the Test Execution for the purpose of adding more context to it.


![image](media://57cd4ca9-a60d-4c25-8d54-7d63824f9bc7)

![image](media://aad9307f-c33e-46e9-b333-ed3069a1622f)

![image](media://5bbc1c25-d02f-4745-aeda-85073c32c87c)

![image](media://d332d469-d514-4306-9fbf-4c59a03e0cbf)

![image](media://c10dfd25-b6cd-4836-8a1c-96ffc6f5a1e8)

![image](media://1b209df4-3a7a-4a3c-862a-05c7f3edda9b)

![image](media://75068421-5234-46ab-97ae-d158b146523c)

## Recommendations

- Don’t reinvent the wheel. Use standard fields, such as labels and components, and avoid unnecessary creation of custom fields.
- Remember that custom fields added to Tests are not copied to Test Runs. Therefore, they’re volatile and informative only; they’re not part of the specification.