100087 - Confirmation when marking bug dupe of bug in another product.

Status: RESOLVED WONTFIX

(Bugzilla :: Creating/Changing Bugs, enhancement, P3)

Description

[Matthew Tuck [:CodeMachine]]

If we mark a bug as a duplicate of a bug in another product, we should confirm
this with the user, as it might be a mistake.

Comment 1

[Bradley Baetz (:bbaetz)]

*** Bug 136850 has been marked as a duplicate of this bug. ***

Comment 2

[Andreas Krüger]

In my opinion, it should be a matter of site parameters to:

* either allow such a thing (as is currently the case), or
* to warn the user who attempts it ("do you really want to do this"), or else
* to completely disallow it.

I suggest "completely disallow" should be the  standard.

For an example of the confusion that can result, see bug 136596, which was 
falsely resolved as a duplicate of bug 108514.  The bugs themselves are luckily 
rather trivial, which in my opinion helps to see the underlying problem better.
(Copied from bug 136050, which was resolved as a dupe of this.)

Comment 3

[Dave Miller [:justdave]]

Enhancements which don't currently have patches on them which are targetted at
2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. 
Consideration will be taken for moving items back to 2.18 on a case-by-case
basis (but is unlikely for enhancements)

Comment 4

[Dave Miller [:justdave]]

Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.

Comment 5

[Frédéric Buclin]

Bah, please don't add another confirmation page. If you mark it as a dupe by accident, you can easily change that later. No need to slow down our workflow for the rare cases where this happens.