Hi, I would like it to be possible to add or rename requirements steps so my workflow is more customized. Could any of you please tell me if there are any updates on this issue/request, since I can see, that it has been an issue for some years now. I think it would be a great help because if we could make the workflow steps/names more aligned with agile process. Br, Karina 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/1666.aspxthreadId=1666Test Management (QualityAssurance@tryg.dk)requirement workflow Hi, I would like it to be possible to add or rename requirements steps so my workflow is more customized. Could any of you please tell me if there are any updates on this issue/request, since I can see, that it has been an issue for some years now. I think it would be a great help because if we could make the workflow steps/names more aligned with agile process. Br, Karina Thu, 27 Apr 2017 14:12:59 -04002024-07-17T13:44:48-04:00/Support/Forum/spiratest/issues-questions/1666.aspxmessageId=2996Jim R (donotreply5@kronodesk.net) Hi Karina It is not currently possible to rename the requirement steps (only the incident steps). It is planned to be possible in the future once we add project template schemes. Regards Jim Tue, 02 May 2017 01:30:16 -04002017-05-02T01:30:16-04:00/Support/Forum/spiratest/issues-questions/1666.aspx#reply2996messageId=3852Piewald Georg (gpi@mission-embedded.com) Any updates on this? I found it requested in other forum entries from 2014, thats 6 years ago! And I dont even see it on the roadmap. The currently defined steps are highly unsuitable for our workflow, which - in my opinion - is nothing uncommon at all. We need two separate review steps, first an internal review and second a review by the customer. To achieve this, we must abuse the existing steps which are a complete misnomer. Wed, 07 Oct 2020 06:56:28 -04002020-10-07T06:56:28-04:00/Support/Forum/spiratest/issues-questions/1666.aspx#reply3852messageId=4076Ilia Poliakov (ilya.polyakov@edetek.com) Yep, cutomization of workflows: Custom status names everywhere adding more/deleting existing, Custom order in filter drop-down on the list view Custom order on the Board is also needed for our company. Mon, 23 Aug 2021 08:27:55 -04002021-08-23T08:27:55-04:00/Support/Forum/spiratest/issues-questions/1666.aspx#reply4076messageId=5813Kamil Kolata (Kamil.Kolata@pta.de) Hello, adding or renaming Requirement steps in workflow - Is this possible and how? Best, K. Mon, 21 Nov 2022 15:14:59 -05002022-11-21T15:14:59-05:00/Support/Forum/spiratest/issues-questions/1666.aspx#reply5813messageId=6818David 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 13:44:48 -04002024-07-17T13:44:48-04:00/Support/Forum/spiratest/issues-questions/1666.aspx#reply6818