A forum for technical support discussion related to Fogbugz.
This is similar, I mean identical, to the following:
This would be *really* useful to us when you release the next version of FB :)
Just my thoughts!
Sunday, February 15, 2009
The solution described here is the most likely support for this use case in FogBugz 7.
The ability to have rich text formatting in every bug edit is something we'd like to offer, but which will not be offered in FogBugz 7 as it's currently envisioned.
Thanks for the update Rich.
The *only* thing that would improve our FB experience in this regard is the ability to selectively use a monospaced font.
Monday, February 16, 2009
Excellent to hear this!
I've been using my own home-grown bug tracking system for nearly ten years now, and one of the biggest things that makes me keep using it in new projects rather than immediately recommending FogBugz (though I do recommend it!) is the fact that it supports a) monospace fonts in the bug descriptions, and b) case-to-case smart linking.
The monospace font thing is done in my case by using a CSS switch for each comment in the thread, simply toggling the style. Proportional | Monospace
This allows you to view each comment in a nice proportional font by default, and switch to monospace if it's a log dump or a formatted table or something else that suffers from HTML's space-collapsing, print-ready nature. It also has a cookie so you can set your default view for all comments.
As for the case to-case linking, that's made easy by the fact that in my system, any case is referred to as an SCR (Software Change Request), so any mention of "SCR #1442" or "scr 533" or whatever matches such a regexp is made into a link. This isn't so easy with FogBugz because "cases" aren't treated with such an easily recognizable moniker; but other packages (such as the open-source Mantis) do have this feature, simply looking for any number of the form "#43225" and making that into a link.
I fully understand the nature of creeping-featurism in a hotly anticipated project, and understand the issues involved with incorporating ideas like this (I think every one of us in the FogBugz user community is familiar with the process, I daresay). But these two things would make my own internal dialogue between "Use my own system on the cheap, or convince management to spring for FogBugz" a heckuva lot simpler. :)
I'd like to point out that FogBugz already automatically smart-links to cases for you. FogBugz uses the expression "case 1", "bug 1", or "BugzID:1." You can even hover over the resulting link to get some extra information about the case in question.
And it should be insanely simple to add monospaced fonts to bug events in FogBugz 7.
Monday, March 16, 2009
This topic is archived. No further replies will be accepted.Other recent topics