Zephyr Essential Data Center: Historical Test Versioning and Test Management

We are currently running Zephyr Essential version 10.3.0.103010235 in our Jira Data Center environment.

One of our project teams has raised concerns about historical test traceability. When they update the steps of an existing test case for a new software release, the changes appear to overwrite the test steps associated with previous releases.

We would appreciate clarification on the following questions:

1. Historical test versioning: Does Zephyr Essential support preserving the original test steps and expected results associated with a completed execution or previous software release when the underlying test case is modified? If so, how can we configure or utilize this functionality?

2. Recommended workaround: If historical test case versioning is not supported, what is the recommended approach to preserving historical test steps across software releases? 

3. Test management interface: We currently have access to the Tests menu, including Search Tests, Plan Test Cycle, and Search Test Executions. What is the recommended method for organizing and managing test cases by project or Fix Version while maintaining traceability across releases?

Ultimately, we would like to establish a workflow within Zephyr Essential that allows our team to update test cases for future releases without losing the historical test steps and execution records associated with previously completed releases.

Thank you for your assistance!