Bug 1348425 - All bugs' activity of field cf_layered_products has gone
Summary: All bugs' activity of field cf_layered_products has gone
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-21 07:10 UTC by Rony Gong 🔥
Modified: 2016-08-05 08:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-05 08:21:17 UTC
Embargoed:


Attachments (Terms of Use)

Description Rony Gong 🔥 2016-06-21 07:10:30 UTC
Description of problem:
All bugs activity of field cf_layered_products has gone

After execute script: bz5-depedent-products.pl
It removed all bugs' activity of field cf_layered_products. 

Please keep this activities.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jeff Fearn 🐞 2016-08-05 01:44:38 UTC
You can't keep history for a deleted field, and if we disable this filed then it's possible some one could re-enable it at a later date, which would be worse than losing the history IMO.

Comment 2 Rony Gong 🔥 2016-08-05 02:14:44 UTC
(In reply to Jeff Fearn from comment #1)
> You can't keep history for a deleted field, and if we disable this filed
> then it's possible some one could re-enable it at a later date, which would
> be worse than losing the history IMO.

cf_layered_products maybe replaced by new name, and this feature still keep. IMO  we'd better keep this field history. Otherwise, after move to BZ5, customers will complain about this once they expect this kind of data.

Comment 3 Jeff Fearn 🐞 2016-08-05 08:21:17 UTC
Customers can't see this data.


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