TestRail 10.6.2 corrects custom-field behavior when its configuration is edited, helping release owners preserve dependable test-data governance. For teams that depend on custom metadata to drive test execution, reporting, and release decisions, this targeted Cloud hotfix addresses a control point that should be predictable.
What changed
The release fixes issue TR-21431, identified in TestRail 10.6.1.1001. The correction applies to the behavior of custom fields when administrators edit their configuration.
This is a maintenance release with a narrow scope. It does not introduce a new operating model for test management; it corrects an existing administrative workflow.
Why custom-field administration is a release concern
Custom fields are frequently more than optional labels. Enterprise teams use them to classify and govern test work, including:
- Product, service, or portfolio ownership
- Risk and business-criticality ratings
- Compliance or control classifications
- Target environment and deployment scope
- Release readiness and approval status
When field configuration changes behave unexpectedly, the effects can extend beyond the administrator making the edit. Test records may be categorized inconsistently, filters may return incomplete views, and reports used in release reviews may no longer represent the intended control model.
The release is small, but the control point matters.
Business and governance impact
For QA leaders, the practical value is lower risk during metadata maintenance. Teams can update field definitions with greater confidence that the intended configuration will be retained and applied correctly.
