Bug 139054 - Cloning a bug to a feature needs some enhancements
Summary: Cloning a bug to a feature needs some enhancements
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 2.18
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-12 19:05 UTC by Suzanne Hillman
Modified: 2013-06-24 02:57 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-05-31 21:16:13 UTC
Embargoed:


Attachments (Terms of Use)

Description Suzanne Hillman 2004-11-12 19:05:28 UTC
This is against bugzilla beta2.

---

When I close a bug to a feature, the information about what version
(RHEL3, for example) the bug was submitted against is completely lost
(because new bugs should be in Target Release "None", Product Release
"New Requests"). I have to add it in by hand.

Additionally, the Component portion of the bug does not get propogated
to the Category field (which is where I suspect that information
should be). It gets put elsewhere (whiteboard?) which does not show up
when you look at the bug later, and which means that the Category
field is empty and complains when you try to submit the bug.

Comment 1 David Lawrence 2005-02-23 07:36:06 UTC
New bug cloning code has been added to the current beta to improve how it works.
Please verify that these are still a problem, otherwise please close this bug
when satisfactory.

Comment 2 Suzanne Hillman 2005-02-25 19:47:11 UTC
I don't seem to have the version being kept, and was fascinated to note that it
now says that it's being cloned against a feature, rather than a bug (which is
inaccurate). I am pleased to note that it now defaults to None and New Requests,
though.

Comment 4 David Lawrence 2007-05-31 20:22:42 UTC
Yes, please. Open a new one for base Bugzilla if still an non-featurezilla issue .


Note You need to log in before you can comment on or make changes to this bug.