most recent 30 from http://fogbugz.stackexchange.com 2013-05-26T09:27:11Z http://fogbugz.stackexchange.com/feeds/question/9736 http://www.creativecommons.org/licenses/by-nc/2.5/rdf http://fogbugz.stackexchange.com/questions/9736/collapsible-entries-in-a-case Michael R. 2011-12-29T17:05:50Z 2013-05-26T02:22:00Z

<p>We congregate stack traces in our cases, which can make the case content very long. So long that any important information added by us developers is almost lost in all the stack traces. I propose collapsible entries. If any entry within the case goes over a certain max length and is not the final entry, collapse it to the max length. Then give the option to expand any one of them, or all of them.</p>

http://fogbugz.stackexchange.com/questions/9736/collapsible-entries-in-a-case/9791#9791 Rich Armstrong 2012-01-11T17:36:58Z 2012-01-11T17:36:58Z

<p>There are a bunch of workarounds for this:</p> <ul> <li>Use BugzScout to capture these stack traces, which will allow you to stop them from appending to the case automatically.</li> <li>For these cases, create a parent case where discussion can happen unmolested.</li> <li>By convention, have all discussion happen via case event edit of the oldest entry.</li> </ul>