Thanks in general for an update. But since this is over 1 year old could you say if things changed?
Also in general @hubspot could you please provide us with an answer why this is not possible? Because via API a timestamp is saved to a date property. Also there is an Option to add delays in minutes / hours etc. after something happened. So all we ask for is to have a separate timefield which can then be used for these delays (for example 2 hours before | 2 hourse after a certain time).
Both combined have over 500 Upvotes. So you can defitnitely say this is one of the highly request features on here. You claim that you will aim to implement the ideas with the most upvotes first. But all we got is a info "not working on this but awesome idea, we consider it..." and this update is 1 1/2 years old in a Thread that exists for over 4 years.
So please at least tell us what is the big road blocker here and why the reason for not implementing this is big enough to disappoint a lot of paying customers with working on a basic feature which all of your competitors have since the beginning?
Openness and giving context can help to clear up a lot of the frustrations that we as your customers have.
@hubspot the datetime field is basic and should've been included years ago. We shouldn't have to rely on API workarounds, hacks, etc. It's 2024 - let's make this a reality.
I can't believe that we are even 4+ years into this request and it's not built....this is WILD. Can anyone in dev just use types and get a time field into here?! My GOODNESS!
Please, help us stop resorting to janky 3rd part products that do not work. We need time of day as a property in releation to meetings and customer properties to be able to trigger workflows and list membership.
