Who would benefit? |
Organizations who need a common choice list custom field that needs to be referenced and consistent across multiple item types. |
What impact would it make? |
This would save time, effort and potential for errors |
How should it work? |
Allow me to create a master picklist that I can "assign" to custom fields across all the Aha! item types, so that we can make a change in one place. Today it takes us 30 min to update all records, and there's always concern we've misspelled something or missed a field in a record. |
Yes, I need exactly this same feature! Allowing record types to share custom fields would be so helpful.
We have use cases for this also. Examples Clinic Locations (50+), Hospital Specialties (50+ choices). Need same list at Initiative, Epic, Feature level and have to manually edit each one individually.