most recent 30 from http://fogbugz.stackexchange.com 2013-05-22T03:52:05Z http://fogbugz.stackexchange.com/feeds/question/10710 http://www.creativecommons.org/licenses/by-nc/2.5/rdf http://fogbugz.stackexchange.com/questions/10710/cannot-set-bugs-to-a-newly-added-priority rtzong 2012-08-15T16:48:23Z 2012-08-24T22:25:07Z

<p>We tried adding a new priority following the instructions written out in <a href="http://fogbugz.stackexchange.com/questions/2162/can-i-add-additional-priorities-to-fogbugz-closed" rel="nofollow">http://fogbugz.stackexchange.com/questions/2162/can-i-add-additional-priorities-to-fogbugz-closed</a>.</p> <p>Our goal was to create a priority even more critical than 1 (because over the course of several years, P1 has lost some of its meaning). We decided to make a P0.</p> <p>However, after going through the steps in the link above, we're finding we can't actually set any of our bugs to the new 0 priority. It shows up in the field as a selectable value, but trying to actually set it just keeps the original priority.</p> <p>It might be relevant to note that the "default" option is tied to this functionality somewhat. First, new bugs will appear to have P0 as default even though it's set to P3. Upon submission, it's actually correctly set to P3. If P0 is the actual default and one creates a new bug, we can successfully set a bug to P0 that way. That is the only way we can create a P0 bug.</p> <p>Any ideas on what might be going wrong?</p>

http://fogbugz.stackexchange.com/questions/10710/cannot-set-bugs-to-a-newly-added-priority/10734#10734 rtzong 2012-08-24T22:25:07Z 2012-08-24T22:25:07Z

<p>We resolved the problem through unconventional methods. This can be closed.</p>