Inflectra Customer Forums: Release Active Flag? (Thread)Is there a way to prevent incidents being assigned to a release that is no longer active? 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/issues-questions/57.aspxthreadId=57Mark Allen (mark.allen@lanint.com)Release Active Flag?Is there a way to prevent incidents being assigned to a release that is no longer active? Tue, 19 Apr 2011 23:56:46 -04002011-04-22T19:39:10-04:00/Support/Forum/spirateam/issues-questions/57.aspxmessageId=119David J (adam.sandman+support@inflectra.com)Incidents cannot be assigned to an Inactive Release. They can only be listed as being detected in suIncidents cannot be assigned to an Inactive Release. They can only be listed as being detected in such Releases.Wed, 20 Apr 2011 18:53:19 -04002011-04-20T18:53:19-04:00/Support/Forum/spirateam/issues-questions/57.aspx#reply119messageId=122Matthew Ferry (matthew.ferry@lanint.com) I know what Mark means. We have to use the "Release Detected In" field as a way of assigni I know what Mark means. We have to use the "Release Detected In" field as a way of assigning an incident to be worked on in a given release. That seems to be what drives defect visibility within a release for the entire app. We use the incident structure for defects and defect management, which I think most customers also do. For example - we find a defect in the current production release and we need to "assign" that defect to the next release coming up in our pipeline so that we can address it. Is there another way to assign an incident to a release? Thu, 21 Apr 2011 20:01:43 -04002011-04-21T20:01:43-04:00/Support/Forum/spirateam/issues-questions/57.aspx#reply122messageId=123David J (adam.sandman+support@inflectra.com) You typically should use the Resolved in Release field to specify the release that the defect is You typically should use the Resolved in Release field to specify the release that the defect is planned to be addressed in. The Detected in Release is only meant to signify the release that the defect was found in . I hope that clarifies things better. Fri, 22 Apr 2011 19:39:10 -04002011-04-22T19:39:10-04:00/Support/Forum/spirateam/issues-questions/57.aspx#reply123