From: Gianluca S. <gi...@gm...> - 2008-05-15 14:37:53
|
Hi everybody, I usually close bugs that looks like support questions asking the reporter to use the tools we have for support, but always stating they are free to reopen the issue and add more information if I misinterpreted their report. Lately I noticed a couple of new bug reports related to closed issues, where the reporter was not able to reopen the closed bug, so I checked the mantisbt.org configuration and here is what we have now: $g_reopen_bug_threshold = DEVELOPER; $g_allow_reporter_reopen = ON; so, unless there's a bug in the reopen logic, they were probably not the reporters of the first bug, but experienced the same issue also after the "fix". I think it is fine to allow the reporter to reopen the bug but I think anyone interested in the bug should be able to do that without opening a new issue. basically, what I'm proposing is to lower the threshold to: $g_reopen_bug_threshold = REPORTER; thoughts? |
From: daryn <da...@ii...> - 2008-05-15 14:56:35
|
Hi all, I agree. If a user experiences a problem and is unable to reopen a bug that matches they are just going to add a new one anyway. I'd much rather see a reopened bug than fill up the bug queue with unnecessary duplicates. On Thu, 2008-05-15 at 16:37 +0200, Gianluca Sforna wrote: > Hi everybody, > I usually close bugs that looks like support questions asking the > reporter to use the tools we have for support, but always stating they > are free to reopen the issue and add more information if I > misinterpreted their report. > > Lately I noticed a couple of new bug reports related to closed issues, > where the reporter was not able to reopen the closed bug, so I checked > the mantisbt.org configuration and here is what we have now: > > $g_reopen_bug_threshold = DEVELOPER; > $g_allow_reporter_reopen = ON; > > so, unless there's a bug in the reopen logic, they were probably not > the reporters of the first bug, but experienced the same issue also > after the "fix". > > I think it is fine to allow the reporter to reopen the bug but I think > anyone interested in the bug should be able to do that without opening > a new issue. > > basically, what I'm proposing is to lower the threshold to: > > $g_reopen_bug_threshold = REPORTER; > > thoughts? > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
From: J. A. B. <bet...@gm...> - 2008-05-15 16:29:59
|
Hi all, I think in the same way, is better to have the option to reopen the bug that create relations between new bugs and closed ones, these leads to confusion. regards On Thu, May 15, 2008 at 9:56 AM, daryn <da...@ii...> wrote: > Hi all, > > I agree. If a user experiences a problem and is unable to reopen a bug > that matches they are just going to add a new one anyway. I'd much > rather see a reopened bug than fill up the bug queue with unnecessary > duplicates. > > On Thu, 2008-05-15 at 16:37 +0200, Gianluca Sforna wrote: > > Hi everybody, > > I usually close bugs that looks like support questions asking the > > reporter to use the tools we have for support, but always stating they > > are free to reopen the issue and add more information if I > > misinterpreted their report. > > > > Lately I noticed a couple of new bug reports related to closed issues, > > where the reporter was not able to reopen the closed bug, so I checked > > the mantisbt.org configuration and here is what we have now: > > > > $g_reopen_bug_threshold = DEVELOPER; > > $g_allow_reporter_reopen = ON; > > > > so, unless there's a bug in the reopen logic, they were probably not > > the reporters of the first bug, but experienced the same issue also > > after the "fix". > > > > I think it is fine to allow the reporter to reopen the bug but I think > > anyone interested in the bug should be able to do that without opening > > a new issue. > > > > basically, what I'm proposing is to lower the threshold to: > > > > $g_reopen_bug_threshold = REPORTER; > > > > thoughts? > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > mantisbt-dev mailing list > > man...@li... > > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > -- ----------------------------------- José Alejandro Betancur http://www.betancur.org |