Upvoted on my part as well.
Our specific use case has 2 pipelines: one for sales and one for outreach to investors. Operated by two different teams and two completely different characteristics of the pipeline and deals within them.
We’ve made some fields required upon deal creation for the Sales team, as otherwise half of the stuff never gets submitted. But as an expected consequence, the team targeting Investors is up in arms because they are now required to submit info that’s nowhere near relevant for their deals.
I love how you’re considering to fix this by implementing that some properties can be set to required based on a value chosen in another. I’ve got some use cases for that as well. First that comes to mind: Closed Lost Reason specification. If Closed Lost Reason was “went to competitor”, make a specification field required: Which competitor?
That granularity helps a lot in reports.