A forum for technical support discussion related to Fogbugz.
I'm evaluating FogBugz and was wondering if the "release note" feature would work for us. We usually maintain several versions of the software in parallel: there is a "trunk" where real developmen happens; from the trunk, a "release branch" for each major version is cut (1.x, 2.x, 3.x, etc.); from each release branch, multiple minor versions are released (1.0, 1.1, 1.2, etc.).
Thus, it often happens that a single bugfix is backported to several versions. For instance, the fix for case #123 might appear in both versions 1.5, 2.3 and 3.0 of the software. What I'd expect is that release notes for all those versions showed the information about the fixed case.
Is this supported by FugBugz?
FogBugz does not currently support this functionality. At this point, release notes are associated with an individual case, and each case is associated with a specific fixfor/release. One clunky workaround is to create a case in each release where you're fixing this bug, resolve all but one of those cases as a duplicate of the main case, and then add a release note to each of those cases. But FogBugz does not have a way to automatically propagate changes to all of the appropriate releases.
We're frustrated with this as well. I'm a bit surprised--as good as FogBugz is--that the notion of a single case applying to multiple branches seems to have been neglected. I think the original poster said it right about their model not being unique.
We're currently on version 4; introducing a new feature that addresses this problem would get us to petition management heavily for an upgrade license. Hopefully release notes would tie nicely into this as well.
This topic is archived. No further replies will be accepted.Other recent topics