1

I am a big fan of the BugMonkey plugin. Especially BugMonkey 2.0 was a huge step: customizations can be edited individually and even enabled on a per user basis. Great!

However, things are getting a bit out of hand. In our installation I currently own 83 customizations. Some of my own, some from this support site, some a mixture of both.

I try to give them descriptive names. But every time I want to change or check something, I have to think hard which customization I need to open. So:

  • I would love to be able to search for some text or css class or whatever

Every now and then I break something. No big deal except... it's impossible to find out what part of which customization I changed. Sure, I could save every customization as a file and check it into our source control system (Visual SourceSafe, don't ask!), but that's not available everywhere. Plus it's very easy to forget. So:

  • why not add history to customizations?

In summary, I would like customizations to be like Wiki pages!

Edit: at least show the last modification date please.

flag

1 Answer

0

I love BugMonkey too! It's great for helping customers tweak their FogBugz installations (and great for scratching personal itches too).

But, writing lots of BugMonkey scripts make a few things painfully obvious:

  1. BugMonkey's current editor isn't nearly as good as [insert your favorite editor here].
  2. Version control for your BugMonkey scripts would be great to have.

So, to help work around these limitations, I wrote up a few tips/tricks I use to make editing and maintaining multiple BugMonkey customizations easier.

link|flag
That's great! But I still would like searching and history "in the browser". – Michel de Ruiter Mar 20 2012 at 8:36
I would too. The good news is that I'm on the FogBugz team, so hopefully I can sneak some of those features into BugMonkey in the future ;) – db Mar 20 2012 at 14:00

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.