<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: Incident Overview Status Field (Thread)</title><description>&#xD;
Hi,&#xD;
&#xD;
    We have set a workflow for incidents within SpiraTest however it looks like a user with the appropriate privileges can actually edit the status of Incidents at the table overview bypassing the workflow. Is there a setting somewhere to turn this off? </description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums/threads</a10:id><ttl>120</ttl><link>/Support/Forum/spiratest/issues-questions/699.aspx</link><item><guid isPermaLink="false">threadId=699</guid><author>Hamzah Saleem (hamzah.saleem@amec.com)</author><title>Incident Overview Status Field</title><description>&#xD;
Hi,&#xD;
&#xD;
    We have set a workflow for incidents within SpiraTest however it looks like a user with the appropriate privileges can actually edit the status of Incidents at the table overview bypassing the workflow. Is there a setting somewhere to turn this off? </description><pubDate>Fri, 30 Aug 2013 15:11:47 -0400</pubDate><a10:updated>2014-06-24T12:48:10-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/699.aspx</link></item><item><guid isPermaLink="false">messageId=1270</guid><author>David J (adam.sandman+support@inflectra.com)</author><title> &#xD;
&#xD;
&#xD;
Hi Hamzah  Absolutely, just give that user 'Modify Owned' permissions instead of 'Modify All'</title><description> &#xD;
&#xD;
&#xD;
Hi Hamzah  Absolutely, just give that user 'Modify Owned' permissions instead of 'Modify All' and it will prevent them bypassing workflow on the incident list page.  Regards  Adam </description><pubDate>Fri, 30 Aug 2013 16:59:55 -0400</pubDate><a10:updated>2013-08-30T16:59:55-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/699.aspx#reply1270</link></item><item><guid isPermaLink="false">messageId=1271</guid><author>Hamzah Saleem (hamzah.saleem@amec.com)</author><title>&#xD;
Hi Adam,&#xD;
&#xD;
    Thanks, that did the trick although I'm in two minds as to whether it would have b</title><description>&#xD;
Hi Adam,&#xD;
&#xD;
    Thanks, that did the trick although I'm in two minds as to whether it would have been nicer to have a way to only disable to 'Status' column in that view. We can assign that to the project owner / admin so it's not too much of a problem. </description><pubDate>Tue, 03 Sep 2013 10:34:04 -0400</pubDate><a10:updated>2013-09-03T10:34:04-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/699.aspx#reply1271</link></item><item><guid isPermaLink="false">messageId=1713</guid><author>Janet McKee (janet.mckee@windstream.com)</author><title> This feature &#xD;
is causing us major issues across all of our projects also.  We need to &#xD;
have a thi</title><description> This feature &#xD;
is causing us major issues across all of our projects also.  We need to &#xD;
have a third option in addition to Modify All and Modify Own.  That &#xD;
option needs to be able to change the owner of the incident and add &#xD;
comments but NOT edit from the list view.  We have development leads &#xD;
that need this capability as they review all of the incidents assigned &#xD;
to their team members, update them with comments, and reassign them to &#xD;
another developer.  Since we have on-shore and off-shore developers, the&#xD;
 person who currently owns the incident is not always available to make &#xD;
these updates. &#xD;
&#xD;
&#xD;
</description><pubDate>Tue, 24 Jun 2014 12:48:10 -0400</pubDate><a10:updated>2014-06-24T12:48:10-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/699.aspx#reply1713</link></item></channel></rss>