We have seen that when creating a requirement, when we create the requirement on any defined release, the Status changes to Planned. I'm assuming this is a workflow step created to say that the status should always be planned when it is assoicated with a release. Is there any way we can change this? We would like to track our test planning process with this Status field, and we have the requirements associated with releases before we start this planning, so it would be nice if we could not default to that planned status when creating the requirements. Any suggestions would be great. 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/spiratest/issues-questions/294.aspxthreadId=294Brett Barker (bbarker@xactware.com) We have seen that when creating a requirement, when we create the requirement on any defined release, the Status changes to Planned. I'm assuming this is a workflow step created to say that the status should always be planned when it is assoicated with a release. Is there any way we can change this? We would like to track our test planning process with this Status field, and we have the requirements associated with releases before we start this planning, so it would be nice if we could not default to that planned status when creating the requirements. Any suggestions would be great. Thanks! Tue, 26 Jun 2012 20:17:05 -04002015-09-08T18:17:39-04:00/Support/Forum/spiratest/issues-questions/294.aspxmessageId=563David J (adam.sandman+support@inflectra.com) Brett Barker when we assign the requirement on any defined release, the Status changes to Planned. I'm assuming this is a workflow step created to say that the status should always be planned when it is assoicated with a release. Unfortunately that is not configurable in the current version. You'd need to either just switch it back from Planned to some other status manually or use a custom property to track it in a different custom status. Fri, 29 Jun 2012 18:18:38 -04002012-06-29T18:18:38-04:00/Support/Forum/spiratest/issues-questions/294.aspx#reply563messageId=2309Hugh Stiteler (hugh.stiteler@mdnllc.net)I'm having the same issue. Your workaround to "just switch it back from Planned to some other status manually" is not a good one, as it makes the release filed blank. This is really a hindrance and should be addressed. I'm using v4.2.0.5. Thu, 03 Sep 2015 13:49:28 -04002015-09-03T13:49:28-04:00/Support/Forum/spiratest/issues-questions/294.aspx#reply2309messageId=2311Kat A (elise.brooks@inflectra.com) Hi Hugh, Not to worry, that reply from Adam is out-of-date. There have been major changes to the requirement functionality since then! Configurable workflow was introduced for requirements, which allows you to customize the status changes, including permissions and field statuses (required, hidden, disabled). Some automatic changes were kept in effect, but there are now flags for them, so that they can be turned off, if needed. Specifically, go to Administration -> Planning -> Planning Options. Then uncheck the Auto-Planned option. That should do the trick! Regards, Elise Tue, 08 Sep 2015 17:10:55 -04002015-09-08T17:10:55-04:00/Support/Forum/spiratest/issues-questions/294.aspx#reply2311messageId=2313Hugh Stiteler (hugh.stiteler@mdnllc.net)That did the trick! Thanks for the tip. Tue, 08 Sep 2015 18:17:39 -04002015-09-08T18:17:39-04:00/Support/Forum/spiratest/issues-questions/294.aspx#reply2313