Page History
...
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 the test executionexample. Some users use it to put the build number/identifier.
Steps Count
Number of Steps in a Manual Test.
...
Associated Tests with the Test Execution.
Test Environments
The Test Environment(s) associated to a given Test Execution. This is an open field, similar to a label; you should try to reuse existing Test Environments. It may be empty (default).
Test Set Status
The "Test Set Status" custom field is a calculated field, usable in the context of Test Set issues, that calculates the "status" (not the workflow status) of all the Tests within the Test Set, for a specific version, having in mind executions (i.e. test runs) for that version. The version that it calculates the status for depends on the behavior for that field defined in a global configuration (see configuration details here).
...
But 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, in the Test Execution you could add a custom field to identify the browser version. Note that, in this example, if you wanted to analyze your Test Execution per browser, it would be preferable to reuse the Test Environments custom field instead; otherwise, you can add some custom fields to the Test Execution if their purpose is just to add more context to it.
Recommendations
...