Bug 196989 - Cloning a bug sets a dependency bug number in new bug to old bug
Summary: Cloning a bug sets a dependency bug number in new bug to old bug
Status: Closed Works As Intended
Alias: None
Product: Services
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Only Me
Assignee: Bugmeister
URL:
Keywords: feature
Depends on:
Blocks:
 
Reported: 2015-01-22 02:16 UTC by Sean Bruno
Modified: 2015-01-22 03:07 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sean Bruno freebsd_committer freebsd_triage 2015-01-22 02:16:14 UTC
No idea why, but cloning an existing bug to use as a template for a new bug sets a dependency on the original bug in the new bug.

Can this be turned off or is that some feature that is used in other freebsd workflows?
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2015-01-22 03:05:42 UTC
Sean,

Looks like this is expected current behaviour.

The behaviour does not look configurable, but I did find an upstream request to make Depends/Blocks dependency behaviour configurable. Adding the relevant Issue ID's to See Also.

I would bump that upstream bug for resolution.

http://bugzilla.readthedocs.org/en/latest/using/filing.html#clone-an-existing-bug