Inflectra Customer Forums: Workflow transition rules are not valid in list view (Thread) Dear all, for my project I implemented an own (reduced) workflow - which was very straight and easy to do... and it works fine in the full detail views. In the list view for all incidents I can edit the data as well. But there I am able to enter ANY status and spira does not care about the defined transitions. Any ideas? BEST REGARDS OLIVER 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/best-practices/690.aspxthreadId=690Oliver Dahms (oliver.dahms@clearstream.com)Workflow transition rules are not valid in list view Dear all, for my project I implemented an own (reduced) workflow - which was very straight and easy to do... and it works fine in the full detail views. In the list view for all incidents I can edit the data as well. But there I am able to enter ANY status and spira does not care about the defined transitions. Any ideas? BEST REGARDS OLIVER Fri, 23 Aug 2013 11:47:57 -04002015-02-09T15:17:14-05:00/Support/Forum/spiratest/best-practices/690.aspxmessageId=1255David J (adam.sandman+support@inflectra.com) Hi Olivier In v4.0 (unlike previous versions), there is a Modify All and Modify Owned permis Hi Olivier In v4.0 (unlike previous versions), there is a Modify All and Modify Owned permission. If you have 'Modify-All' then you can edit all the incidents in the list and in addition bypass workflow using the list page. If you only have Modify Owned permission, then you can only edit the ones detected or assigned to you, in which case you cannot edit them at all on the list page and the workflow is enforced. Regards Adam Mon, 26 Aug 2013 03:26:20 -04002013-08-26T03:26:20-04:00/Support/Forum/spiratest/best-practices/690.aspx#reply1255messageId=1712Janet McKee (janet.mckee@windstream.com)This feature is causing us major issues across all of our projects also. We need to have a third opThis feature is causing us major issues across all of our projects also. We need to have a third option in addition to Modify All and Modify Own. That option needs to be able to change the owner of the incident and add comments but NOT edit from the list view. We have development leads that need this capability as they review all of the incidents assigned to their team members, update them with comments, and reassign them to another developer. Since we have on-shore and off-shore developers, the person who currently owns the incident is not always available to make these updates. Tue, 24 Jun 2014 12:43:01 -04002014-06-24T12:43:01-04:00/Support/Forum/spiratest/best-practices/690.aspx#reply1712messageId=1894Jon Freed (jfreed@edmap.com) We have also noticed how workflow is executed differently in list views versus edit-details views. We have also noticed how workflow is executed differently in list views versus edit-details views. It is very problematic. We would like the rules to be consistent. We would prefer that "Modify All" not be able to overrule workflow rules. That being said, it would be nice to for administrators to still be able to overrule workflow rules. Wed, 22 Oct 2014 13:14:47 -04002014-10-22T13:14:47-04:00/Support/Forum/spiratest/best-practices/690.aspx#reply1894