Renaming a custom field value causes the Kanban exit policy to be hidden

Document ID : KB000124120
Last Modified Date : 04/01/2019
Show Technical Document Details
A customer created a custom field (value) with a given name, and created a Kanban Board based on it.   They added an exit policy or agreement verbiage to the board.  They then renamed the field (value to a more specific / less generic name), and adjusted the Kanban Board's settings (mapping) to use the renamed custom field. The exit policy (agreement) verbiage disappeared.  Upon renaming the field/value back to its original name, the policy verbiage reappeared.  Is this defective?
While it may appear to be defective and is an inconvenience, the exit policy entered for a specific field name or value is associated to that value only.  The user will need to re-enter the policy verbiage as part of the process when renaming fields or values.  The fact that the policy verbiage is restored when reverting the field name/value this is evidence that the verbiage is associated specifically to that prior value.  Additionally changes to field names and values will also remove the column mapping on the Kanban Board for any fields/values that are altered in this manner.  This is working as designed.