Question

Not exactly a huge vote of confidence for the built-in wiki if you guys aren't using it for your own documentation. What's the deal?

Answer 1

FogCreek uses the wiki feature internally, to

• Write about the projects that we're working on
• Create technical specifications
• Document our internal policies and procedures
• Create reports for various initiatives
• ... and pretty much any other document that we want to collaborate on and publish internally.

We do expose some portions of our wiki (e.g. FogBugz ecology) and use a wiki on a separate FogBugz On-Demand account (developers.fogbugz.com) for all of our plug-in API documentation, which is our public vote of confidence for using the wiki portion of FogBugz for documentation.

The admittedly sorry state of current FogBugz documentation is something we're committed to tackling, but it probably won't be through the wiki.