Clearly illustrate when there are inherited fields and values when adding new custom fields.

My team manages several products in a hierarchical company/product group/individual product hierarchy. We also make heavy use of custom fields.

When adding a new custom field, it's not immediately apparent what will already be inherited by the product group or product in question.

As a concrete example, I added a custom field 'External Visibility' to the product group that I manage while my manager had added the same field to the company as a whole. As a result, we had two 'External Visibility' fields added which confused everyone.

  • Sam Kerr
  • Sep 14 2016
  • Shipped
Release time frame
  • Attach files