Sean Laurent wrote:
> On Tuesday 18 January 2005 01:45 pm, Nick_Gianakas@sybari.com wrote:
>>A nice feature here would be to have an issue split itself (emulate
>>multiple copies) per attribute (platform, release, etc). That's probably
>>what you're looking for. I don't know of an issue tracker that does this.
> Mantis (http://www.mantisbt.org) provides the closest to this I've seen in a
> You can create a clone of an issue and tie the two issues together with a
> dependency relationship ("related to", "depends on", "prereq of", etc.):
> - Create a general issue for the bug (let's say issue #42)
> - Create a clone (#43) that's a child of #42. In other words, #43 blocks #42
> until #43 is marked as complete. Make #43 for release X.
> - Create another clone (#44) that's a child of #42 and make it for release Y.
> Now, Peter Valdemar Mørch originally requested:
>>- "I know bug # X has been fixed on branch Y. But has
>>it been fixed on branch Z? Was it ever present on branch Z?"
>>- A tool that can keep track of what branches the bug applies to / is
>>relevant for, and what branches it has been fixed on - either because
>>it has been manually fixed on several branches, or because the fix
>>has been merged from one branch to another.
> Unfortunately, Mantis doesn't help with this at all.
> However, Pete also wrote:
>>At least in the tools I know of, I can not get it to show that it
>>originally applied to releases X, Y and Z, but is fixed in X only.
> If you're willing to do the manual work of outlining which releases you ~know~
> contain the bug, then my aforementioned solution in Mantis might work for
> you. I would guess other bug tracking packages provide similar
> functionality, so you might be able to adapt that strategy and at least
> improve your issue tracking a little bit.
The Ingres system was integrated with the issue tracker and so did
indeed maintain open issues per "variant". Sigh, if only we could prise
it free from the current owners.....
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Jan 18 21:24:46 2005