As Spira is release based, it is quite important to link the test sets to the correct release. Sometimes this is forgotten to set. Is there a way to enforce this? Can this field be set to mandatory? for example in the template Thanks en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/best-practices/2917.aspxthreadId=2917kim vijle (kvij@idirect.net)test set release As Spira is release based, it is quite important to link the test sets to the correct release. Sometimes this is forgotten to set. Is there a way to enforce this? Can this field be set to mandatory? for example in the template Thanks Tue, 07 May 2024 09:32:09 -04002026-04-10T09:47:55-04:00/Support/Forum/spirateam/best-practices/2917.aspxmessageId=6680David J (adam.sandman+support@inflectra.com) Hi Kim Currently there is not a way to enforce that Release is set on a Test Set. Please log a ticket and one of our support engineers can log it as a requested enhancement. Regards David Tue, 07 May 2024 10:59:17 -04002024-05-07T10:59:17-04:00/Support/Forum/spirateam/best-practices/2917.aspx#reply6680messageId=7593Gene Nelson (Gene742Nelson@outlook.com) Hello! In Spira you can enforce linking test sets to a release by marking the Release field as required in the Test Set template under Administration. That way, users cannot save or move a test set forward without selecting a release. The only trade‑off is that every test set must have a release assigned, but this is generally beneficial since it ensures proper traceability and reporting. Without it, you risk incomplete coverage data and weaker release‑based reports. Fri, 10 Apr 2026 09:47:55 -04002026-04-14T08:30:28-04:00/Support/Forum/spirateam/best-practices/2917.aspx#reply7593