0004730: Adding a duplicate relationship and closing issue - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0004730	mantisbt	relationships	public	2004-10-18 07:58	2013-03-13 06:17

Reporter	DGtlRift	Assigned To
Priority	low	Severity	feature	Reproducibility	always
Status	new	Resolution	open

Summary	0004730: Adding a duplicate relationship and closing issue
Description	When adding a duplicate relationship, the newer issue (higher issue number) should automatically close. In addition, the older issue should include the notes of the the duplicate issue but also indicate that they are from the other issue. This would save hunting around to locate all the notes and slightly diffrent point of views that lurk amongst all the duplicate issues.
Tags	No tags attached.

dmandell 2004-11-05 15:38 reporter ~0008254	I don't know if adding notes from the newer bug to the older bug makes sense, if it's a dup is it really necessary? I do however agree with closing the bug as duplicate when creating a duplicate relationship. What used to be a simple process before (close the bug, mark it a duplicate, enter duplicate bug id#, save) now requires work on multiple pages process (set relationship as duplicate, enter dup bug id, save, edit bug, close and mark as duplicate). Are there really any instances where you're marking a bug as a dup but you want to leave it open?