It would be nice that within the pipeline flow we could place mandatory properties as it can be done today but that depend on another property, if I have a customer that I know visits my branch, the date is mandatory but if he does not visit it, it is not, for instance
Its a good idea, we are look for a similar solution.
nice! we also look für a solution!
Great suggestion!
Another use case would be:
If “Requires PO Number for Billing” is ‘Yes’, then make “PO Number” mandatory.
And there is a significant number of times I found business needs that would be simply covered by this conditioning but had to say it couldn’t be done.
Any update on this request? We have a similar need where field-2 needs to entered only when a particular option is selected in the field-1. Any color if very much appreciated.
Yes please to this. Would make a lot of people here very happy and less stressed 
This feature is much needed. I hope you’ll add it to your product roadmap soon
Agreed - we have a pretty diverse business and different pipelines to match. There are many properties that are only important on certain conditions and I don’t want to ask for property updates if those conditions aren’t met, it would be way too many.
This would be a game changer.
Get this done ASAP.
This would be really helpful! We currently use quite a lot of non-mandatory properties, but this is not user-friendly and we have no control over how we enforce data entry.
We also have a use case for this idea. We only want properties to be required in the pipeline if another property meets criteria.
Following up on this as it’s a feature that has been requested for almost three years. HubSpot team - is this on the feature road map?
How has this not been done yet? Feels like very basic CRM configurability.
Just adding to see if there’s been any movement on this at all given the idea was submitted nearly 3 years ago!
Still very needed, our whole business is based on different pipelines. We should be able to use diverse conditional logic.
This logic would be incredibly useful and significantly reduce the number of complicated duplicate pipelines that need to be created/used just to include a required field under a certain condition.
It seems fairly simple given all of the other places we can now set up Conditional Fields. i.e. if Billing Frequency is Monthly then require Monthly Payment Amount at the Contract stage. If the Billing Frequency is Annual, then don’t show the Monthly Amount field.
Adding another comment for visibility. Depending on the service line, we have different information that’s required at different stages.
Adding another comment for visibility. This has been a blocker for us.
How does this not exist? We sell to multiple personas, and the information we need to know for those different personas differs meaningfully. Using separate pipelines doesn’t work because we don’t know until after the first call