Closed Bug 518932 Opened 16 years ago Closed 16 years ago

Would like a way to track which bugs a bug was cloned from

Categories

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

Product:
Bugzilla
Component:
Creating/Changing Bugs
Type:
enhancement

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: gregaryh, Assigned: gregaryh)

References

Details

Attachments

(1 file)

V1
10.49 KB, patch
Details | Diff | Splinter Review
Currently, cloning a bug creates a dependency with the cloned bug. However, this is not always desirable. In fact, we usually don't want a dependency because the cloned bug really needs to be a separate entity. However, we would still like to be able to track which bugs were clones. Currently there is no better option to track this than to search the comments (which might have also been edited out). I propose creating a separate link to bugs that are cloned from other bugs such that any bug can know where it was cloned from as well as what bugs were cloned from it without creating a dependency.
Attached patch V1 — — Splinter Review
Tracking clones is almost identical to tracking dupes. This patch takes that as a premise.
Assignee: create-and-change → ghendricks
Attachment #402923 - Flags: review?(mkanat)
Mmm, I kind of think that this should be WONTFIX'ed in favor of Bug 55970.
OS: Linux → All
Priority: -- → P5
Hardware: x86 → All
(In reply to comment #2) > Mmm, I kind of think that this should be WONTFIX'ed in favor of Bug 55970. Yes, I agree. WONTFIX!
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
Target Milestone: Bugzilla 3.6 → ---
Attachment #402923 - Flags: review?(mkanat)
Perhaps depends-on would be better, helps for the searching... I'll leave it up to the bugzilla folks to reopen.
Depends on: bz-branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: