A forum for technical support discussion related to Fogbugz.
The wiki's nice; cases are nice; but, except for auto-linking to cases, I don't see much integration between them. These integrations would help me a great deal:
(1) Treat the body of a case as a wiki page. This subsumes the feature request of allowing rich text in a case, as well as the request to allow case bodies to be editable. It does that in a way that provides a uniform interface in FogBugz.
(2) Add "New Case" to the "Insert" menu in the wiki editor. This would support "recursive descent" design, in that I could start out editing the design doc or (given feature 1) the case for a top-level feature, then add in links to the smaller tasks as it came time to refine them.
Tuesday, February 3, 2009
1.) Check this out: http://our.fogbugz.com/default.asp?fogbugz.4.38805.6
2.) Filing a feature request. This is a good idea.
Thanks, Rich. On the question of editable case bodies, count me in with the group asking for the (optional) ability to have the main case description be editable; that is, I wouldn't be happy with just having a linked wiki page I need to jump to, disconnecting me from all the other information in the case.
An ugly but straightforward way to allow fixed case descriptions (as now) in parallel with editable case descriptions is to give each case both fields. Those who want the flexibility to edit would fill in all the information in the mutable description and ignore the fixed description; those who wanted the rigor of all modifications coming through comments would fill in only the fixed description. Cases created out of email could fill in the fixed description, thus getting around the problem of rich editing being associated with needing to parse HTML email.
I don't know how to do "me too" on old topics (adding a "thumbs up" or "thumbs down" button to each topic would be helpful), but count me as a supporter of roll-up cases, wherein the time estimate for the roll-up includes a sum of the time estimates for all the children, and priorities and deadlines propagate from the parent to the children. That's related to this post only in that it's helpful to support recursive descent design, which I sometimes need to do.
Friday, February 6, 2009
This topic is archived. No further replies will be accepted.Other recent topics