'related to' bugs vs. dependent bugs
lyhenry at speakeasy.net
Thu Aug 30 17:23:20 UTC 2007
Thanks, I'll watch that bug. Sounds like this is a useful feature for
others, as well.
Max Kanat-Alexander wrote:
> On Wed, 29 Aug 2007 18:25:16 -0700 Lisa Henry <lyhenry at speakeasy.net>
>> One of our groups uses bug cloning in their workflow, but the bug
>> dependency that is set up is not always what they want. We have
>> 'noresolveonopenblockers' turned on. A user poll showed that some
>> people do want the resolution blocking feature, others find it
>> annoying, and just clear the 'blocks' or 'depends on' field in order
>> to resolve the bug. Several users suggested that a third field
>> (something like 'related to') along with the 'blocks' and 'depends
>> on' would be a solution. We would want the tree view and graphing
>> capability, but would not want related bugs to block resolution.
> That sounds like you just shouldn't be using
>> Before I start looking into this, does anyone have suggestions as to
>> the best way to accomplish this? I've done a bit of customization,
>> but prefer not to if there is a more supported method.
> We've had some discussion about it (about 8 years worth,
More information about the developers