FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at

Posts by Fog Creek Employees are marked:

Release Notes
Network Status

How to edit a case to delete inadvertently-introduced errors?

I am pretty new to Fogbugz (on 7) and was trying to do a bulk operation.  That did not work as expected, and somehow a copied set of cases landed in the midst of an unrelated case as an edit to it.  Do I have any way of scrubbing this info out of the affected case?  If not, what is the most gracious way to handle it now?
Andrea Miller Send private email
Wednesday, March 17, 2010
Check out the ScratchOut plug-in.

We are working on case edit for a future version.
Rich Armstrong Send private email
Wednesday, March 17, 2010
Thanks!  Now I need to ask whether anybody else needs to use the same plug-in to view the case I may be scratching info out of - or once the effects of the plug-in are applied, then anybody can see them whether they have implemented the plug-in or not?
Andrea Miller Send private email
Thursday, March 18, 2010
The latter... "anybody can see them whether they have implemented the plug-in or not".  The plugin is a system wide thing, so it will be installed for everyone.
Michael H. Pryor Send private email
Friday, March 19, 2010
Further questions:  what permissions need to be set to download a plug-in?  I am established as a user of FogBugz with at least sufficient Administrative rights to create public snippets but when I am asked to log in to the Fogcreek site to download the ScratchOut plug-in, my FogBugz login and password are not recognized.  Should the request for the plug-in be taken to a higher level of authority?
Andrea Miller Send private email
Friday, March 26, 2010
YOu shouldn't need to have a username or password to download any plug-in here:

If you're on OnDemand (your URL ends in, then you just enable plug-ins rather than uploading.
Rich Armstrong Send private email
Saturday, March 27, 2010
Thanks, my URL does end in but I am not sure just how to enable a plug-in.  Can you detail any specific steps to take to do so?  The URL provided in this thread of
 says what FB_ScratchOut is, and has an Install button but I am perhaps missing what to do to just enable it.  Generally I would login to FogBugz through my URL to see my cases.  What do I need to do at that point to be ready to use FB_ScratchOut?  Also, if I were to enable it, would it then affect any other session that someone else would open under our URL or is it just for that specific session that I am actively on that it will work for to take the deprecate action necessary?  Finally, if I deprecate references to other cases from within the specific case where they got referred to in error, does it affect those other cases in any way?  Many thanks!
Andrea Miller Send private email
Saturday, March 27, 2010
I did figure out how to enable a plug-in and have been successfully using the ScratchOut plug-in.  Where is the best place to take my questions about how this specific plug-in behaves (compared to how I thought it would).  Right here on this thread?  Or should I start a new thread?  Or is there another forum entirely to ask in?

Just in case, the gist of my question is that the ScratchOut visually strikes through the undesired info, but if that info contains references to other cases, those cases are still available live despite having been struck through (in other words, the See Also does contain the cases and the association with the case edited by ScratchOut remains even though I did not want it to).  Is this farther than ScratchOut was meant to take the deprecation, or is this part of what ScratchOut should be doing?  Thanks in advance for any clarification.
Andrea Miller Send private email
Tuesday, March 30, 2010
the author of that plugin is active on  I'd start there.
Rich Armstrong Send private email
Monday, April 5, 2010

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.