The requirements Workflow Steps appear to be fixed to a set of steps. Is there a way to create new steps similar to the way they can be created in the Incident Workflow? Is there a way to rename requirement steps similar to the way they can be renamed in the Incident Workflow? Maybe this can't be done directly from the UI but done in the database? 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/941.aspxthreadId=941Hugh Stiteler (hugh.stiteler@mdnllc.net)workflow requiremens The requirements Workflow Steps appear to be fixed to a set of steps. Is there a way to create new steps similar to the way they can be created in the Incident Workflow? Is there a way to rename requirement steps similar to the way they can be renamed in the Incident Workflow? Maybe this can't be done directly from the UI but done in the database? Thu, 26 Jun 2014 18:17:34 -04002024-07-17T20:08:10-04:00/Support/Forum/spiratest/issues-questions/941.aspxmessageId=1724Jim R (donotreply5@kronodesk.net) Hi Hugh There is not currently a way to add/change requirement steps (unlike incidents). We are considering adding this feature in a future release, but for now it is not supported. Changing it directly in the database is not supported nor recommended either at present. Regards Jim Thu, 03 Jul 2014 15:11:33 -04002014-07-03T15:11:33-04:00/Support/Forum/spiratest/issues-questions/941.aspx#reply1724messageId=1822Steve Pelikan (steve.pelikan@wizards.com) Please add a big +1 (more like +200 users) for this functionality. We definitely need the ability to add/rename requirement workflow statuses.Thu, 11 Sep 2014 22:27:57 -04002014-09-11T22:27:57-04:00/Support/Forum/spiratest/issues-questions/941.aspx#reply1822messageId=1991thomas mera (tmera@glneurotech.com) I second that, being able to add new rq workflow steps would be a big help Wed, 31 Dec 2014 14:28:20 -05002014-12-31T14:28:20-05:00/Support/Forum/spiratest/issues-questions/941.aspx#reply1991messageId=2134Olli Mensio (olli.mensio@nls.fi) thomas mera I second that, being able to add new rq workflow steps would be a big help Is there any plans about this issue? BR. Olli Mensio Tue, 02 Jun 2015 10:36:36 -04002015-06-02T10:36:36-04:00/Support/Forum/spiratest/issues-questions/941.aspx#reply2134messageId=6837David J (adam.sandman+support@inflectra.com) Following up on this thread. When we introduced product templates we made most of the statuses, all of the types and all of the priorities customizable. We didnt make the following three artifacts statuses customizable: Test cases Requirements Tasks This was because of the interconnections between them and the business rules that link them: When a release is assigned to a requirement, the status changes to Planned When all tasks are completed, the requirement status changes to Developed When all test cases are passed, the requirement status changes to Tested Allowing these to be customizable and also have the linked business rules was deemed to be too complicated for the release in question. Now with the advent of SpiraApps, it will be possible to allow customers to configure relationships between workflows more easily, so the longer-term plan is to reconsider making these customizable and use SpiraApps to integrate the flows. We are definitely aware of the need, and see it as a high priority going into 2025. Wed, 17 Jul 2024 20:08:10 -04002024-07-17T20:08:10-04:00/Support/Forum/spiratest/issues-questions/941.aspx#reply6837