most recent 30 from http://fogbugz.stackexchange.com 2013-06-19T09:49:51Z http://fogbugz.stackexchange.com/feeds/question/9243 http://www.creativecommons.org/licenses/by-nc/2.5/rdf http://fogbugz.stackexchange.com/questions/9243/feature-request-allow-custom-fields-to-be-editable-on-closed-cases vitalyb 2011-09-21T08:54:01Z 2012-08-06T15:27:52Z

<p>We've decided that to track which case belongs to which (released) version we are going to use the "Version" field in FogBugz. </p> <p>The workflow is as following: Start each case with a blank version, then when we've decided to release a new version of our product, we update all closed cases with blank version field to the newly released version.</p> <p>However, upon trying to do so in FogBugz we've stumbled upon an issue: "Version" field is read-only once the case is closed.</p> <p>Options and alternatives:</p> <ul> <li><strong>Version field</strong> - We can use the version field, if we either leave the case at resolved or reactivate the cases before updating the version field. Both options are bad in my eyes.</li> <li><strong>Custom fields</strong> - I've figured I could create a custom field that would be editable when the case is closed (note: when the case is CLOSING, the field is available. However, when it is closed it isn't). However, the custom field seems to read-only when the case is closed and there is no option to make it available.</li> <li><strong>Release Notes</strong> - This seems like a relatively good choice since "Release notes" is available for closed cases and we don't use it for anything else. However, "Release notes" aren't visible in the grid. Moreover, I can't update release notes when I am editing several cases at once.</li> <li><strong>Tags</strong> - This is currently the only option I see. Tags are available to closed cases, visible in grid and can be multi-edited. However, I'd prefer a more specialized field for this (e.g Version), especially since we do use tags occasionally for other stuff.</li> </ul> <p><strong>Custom fields clarification</strong></p> <p>To clarify the issue with custom fields, here is a screenshot of creating a custom field:</p> <p><img src="http://dl.dropbox.com/u/34935/%7B4812%7DScreenshots/2011-09-22_07-38-27.png" alt="Creating custom field"></p> <p>And here is what it looks like when I try to edit a closed case, note that I have no ability to edit TestField:</p> <p><img src="http://dl.dropbox.com/u/34935/%7B4812%7DScreenshots/2011-09-22_07-42-07.png" alt="Editing closed case"></p> <p>I'd be happy to hear of other alternatives and options.</p> <p>Thanks!</p> <blockquote> <p><img src="http://www.gravatar.com/avatar/baf927dcc0b0c5d0f41dece1e575aa0f?s=32&amp;d=identicon&amp;r=PG" alt="Fog Creek"> <a href="http://fogbugz.stackexchange.com/questions/1023/whats-that-kiwi-logo-and-case-number-at-the-bottom-of-my-feature-request" rel="nofollow">Case FC2323033</a></p> </blockquote>

http://fogbugz.stackexchange.com/questions/9243/feature-request-allow-custom-fields-to-be-editable-on-closed-cases/9253#9253 Rich Armstrong 2011-09-21T17:21:53Z 2011-09-22T13:46:00Z

<p>This is a good point. We'll file it as a feature request when it reaches our top 100 requests by votes. Thanks!</p>