Inflectra Customer Forums: Change Request(?): Do not display inactive Releases and Iterations in dropdowns in Requirements, Incidents, etc. (Thread) Some of our Releases and Iterations are inactive. However, they are still displayed in dropdowns such as the Incident "Detected Release" and "Resolved Release" dropdowns. This is confusing for users. Is there a way to prevent inactive releases and iterations from being displayed in such dropdowns? If not, please consider this to be a change request for a future release. en-US(C) Copyright 2006-2024 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/1138.aspxthreadId=1138Jon Freed (jfreed@edmap.com)inactive releasesChange Request(?): Do not display inactive Releases and Iterations in dropdowns in Requirements, Incidents, etc. Some of our Releases and Iterations are inactive. However, they are still displayed in dropdowns such as the Incident "Detected Release" and "Resolved Release" dropdowns. This is confusing for users. Is there a way to prevent inactive releases and iterations from being displayed in such dropdowns? If not, please consider this to be a change request for a future release. Fri, 23 Jan 2015 15:32:26 -05002015-01-27T19:30:53-05:00/Support/Forum/spirateam/issues-questions/1138.aspxmessageId=2027Kat A (support2@inflectra.com) Hi Jon, By design, inactive releases are still available in the incident "Detected Release" Hi Jon, By design, inactive releases are still available in the incident "Detected Release" dropdown, since an incident may be reported against an old release that has been made inactive. However, I believe that's the only dropdown that includes them. If you are seeing them in other dropdowns, let us know. It's possible there is a bug. Regards, Elise Tue, 27 Jan 2015 19:30:53 -05002015-01-27T19:30:53-05:00/Support/Forum/spirateam/issues-questions/1138.aspx#reply2027