Allow Dropdown Dependencies on standard fields

​@revathimenon could we get the current PM 👀 on this?

As ​@darkknight mentioned there are work arounds, and we are aware of them, but it adds unnecessary complexity and, what Gainsight probably cares more about - user friction. We have to create more fields and things for users to click to do something that standard fields should be able to accomplish.

Sure, we can set the default value of “Reason” to something when we want a “Reason” picklist that controls another picklist to be used instead, but it really creates an inconsistent user experience, and forces admins to bifurcate what should be a simple, fluid process into “CTAs that can use the Reason Field” and “CTAs that can’t use the Reason field”.

It is also terrible for reporting, which causes friction with leadership because reports are more confusing and/or harder to make.

So, now we have annoyed both our key user groups: end users and leadership. Effective, yes. Desired, no.