Xray uses different issue types for implementing the testing process (with the exception of Test Runs).
That means that you are able to manually log time on those issues, using JIRA out-of-the-box. And if you have some other apps or integrations that are based on this field, then you are going to have it available there also.
Some reports (e.g. Test Runs Report, Test Executions Report) use the elapsed time from each Test Run. This time is not logged in JIRA automatically.
Please note
Only some issue types have time tracking enabled by default: Test Execution, Test Plan.
However, if you want, you can then easily add Time Tracking features to the other issue types (Test, Pre-Condition, Test Set), by editing the respective view/default screens and add the "Time Tracking" field.
Possible usage scenarios for logging time
| Issue type | Purpose | Notes |
|---|---|---|
| Test | log time related with specification | don't log time here related with execution, since Test issues are like test templates |
| Pre-Condition | log time related with specification | |
| Test Set | log time related with creation of Test Set, eventualy considering the time related with the specification of related Tests and Pre-Condtions | |
| (Sub)Test Execution | log time related with the execution of related Test runs | |
| Test Plan | log time related with environments setup, planning |
Possible usage scenarios for using time estimates
| Issue type | Purpose |
|---|---|
| Test | estimated execution duration for this Test |
| Pre-Condition | estimated execution duration for ensuring this Pre-Condition |
| Test Set | estimated time for specifying all the Tests being grouped within this Test Set |
| (Sub)Test Execution | estimated time for running all the related Test Runs |
| Test Plan | estimated time for all the effort associated with the validation of the Tests within the plan, including environment setup and multiple iterations |