The default bug view has changed. See this FAQ.

A bug marked as duplicate of a duplicate should also display the bug at the end of the duplicate chain

NEW
Unassigned

Status

()

Bugzilla
Creating/Changing Bugs
P3
enhancement
8 years ago
4 years ago

People

(Reporter: zwol, Unassigned)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

8 years ago
If Bug A is resolved as a duplicate of Bug B, and then Bug B is resolved as a duplicate of Bug C, A should appear to be a duplicate of C from then on.  Similarly, if B is already a duplicate of C when someone resolves A as duplicate of B, A should immediately appear to be duplicate of C.

The cc: lists should also forward in this fashion.

Bug 112532 appears related.

Updated

8 years ago
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3

Comment 1

5 years ago
Created attachment 610572 [details] [diff] [review]
patch, v1

This patch is about the first part of your request. The 2nd part about the CC list has already been requested in bug 108983.
Assignee: create-and-change → LpSolit
Status: NEW → ASSIGNED
Attachment #610572 - Flags: review?(glob)

Updated

5 years ago
Summary: Duplicates should show the end of the chain → A bug marked as duplicate of a duplicate should also display the bug at the end of the duplicate chain
Target Milestone: --- → Bugzilla 4.4
this works, but i'm not totally sold on the wording.

what are your thoughts on displaying the ultimate bug as primary, mentioning intermediate bug(s) secondarily.

so when bug A is dupes to bug B, which is then duped to bug C, bug A would display as:

  RESOLVED DUPLICATE of bug C (via bug B)
Comment on attachment 610572 [details] [diff] [review]
patch, v1

r- for reasons stated in comment 2.
Attachment #610572 - Flags: review?(glob) → review-

Comment 4

5 years ago
We are going to branch for Bugzilla 4.4 next week and this bug is too invasive or too risky to be accepted for 4.4 at this point. The target milestone is set to 5.0 which is our next major release.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else on time for 5.0.
Target Milestone: Bugzilla 4.4 → Bugzilla 5.0

Updated

4 years ago
Assignee: LpSolit → create-and-change
Target Milestone: Bugzilla 5.0 → ---

Updated

4 years ago
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.