Bug 1320235 - Custom fields should be removed when a bug is cloned bug that can't use it
Summary: Custom fields should be removed when a bug is cloned bug that can't use it
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: 5.0
Assignee: Jeff Fearn 🐞
QA Contact: Jeff Fearn 🐞
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-22 15:36 UTC by Sandro Bonazzola
Modified: 2025-10-16 23:45 UTC (History)
3 users (show)

Fixed In Version: 5.0.4-rh2
Clone Of:
Environment:
Last Closed: 2018-04-18 10:14:51 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1323778 0 medium CLOSED Cannot re-assign bugs to products with a mandatory custom field 2025-10-16 23:45:36 UTC

Internal Links: 1323778

Description Sandro Bonazzola 2016-03-22 15:36:30 UTC 
Description of problem:
cf_ovirt_team = integration has been kept on bug #1304973 when cloning from bug #1300959

cf_ovirt_team can't be changed / removed from bug #1304973 using the web ui.

expected behavior: don't copy cf_ovirt_team to different product / classification while cloning a bug.
Comment 1 Jeff Fearn 🐞 2017-10-10 02:00:43 UTC 
This is a general rule and any CF should be removed from a bug if that CF isn't visible on the product it's being moved to.
Comment 2 Jeff Fearn 🐞 2018-04-11 06:33:48 UTC 
CFs are set to default value when bug is cloned to a product not using that CF.
Comment 3 Jeff Fearn 🐞 2018-04-18 10:14:51 UTC 
This bug has been resolved in Red Hat Bugzilla 5 and can be tested on https://beta-bugzilla.redhat.com

If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.
Note You need to log in before you can comment on or make changes to this bug.