Following up on this with a new thread to make absolutely sure that the dev team and/or management sees this. As of 2023-05-20T16:47:00Z, automations are still unable to read the TIME value stored in date fields. This goes for all automations, date fields, columns, boards, and workflows. The TIME value is stored in the date field of course, but even custom automation apps like column magic don’t work because Monday is (somehow) unable to reference that stored TIME value no matter what the actual desired behavior or use-case is.
I’ll be honest, after seeing all the threads pointing out this issue going all the way back to 2020, I’m ready to drop the platform. Unfortunately, this is an extremely simple thing to achieve and it indicates significant problems in tech debt and/or management that signal danger for our agency to continue using it. If something that basic isn’t addressed, then I can’t trust the actually difficult things to ever get addressed. If 2.5 years wasn’t enough for this feature, then it’s not coming.
Please convince me otherwise. Please guys. Just fix this in an afternoon. I seriously don’t want to rebuild everything with Asana + Zap. I’m begging you. This is so easy. You’re one distro push away. For all that is holy and good, please fix this guys. It’s not worth losing the lifetime of revenue that I have to spend to scale this agency. It’s not worth it. Please fix it. Just make it read the time value that’s already there. Please.
We appreciate you taking the time to write this feature request and apologise to hear of your frustration.
We have followed up directly with the developers on this request, who are aware that there is demand for this feature and are certainly working on bringing this functionality to life. That said, the release of this feature is dependent on further developments of our new mondayDB that will expose capabilities needed to build the date filter/scheduling functionality. We assure you that your comments are being heard and noted internally. Our developer team hopes to consider this features development later this year
If we are provided any further information or updates, rest assured they will be shared here.
Not sure if this is the right place to put this but the fact that the automation cannot trigger based on the item’s designated date and time is ridiculous, and goes against all logic as to having the automation trigger in the first place.
For example, I’m trying to have a notification go out to the item’s assignee at the date and time of an appointment field, in order to remind the person responsible for that appointment to update the status of the appointment. I should be able to choose the date and time of the appointment, and then how many minutes, hours, days etc after that date and time the notification is sent.
Are you atleast impressed at how quickly the dev team churned out useless AI features?
Or perhaps the overblown conferences that highlight nothing of use?
I’m personally relieved that the increase to the convoluted and anti-consumer payment subscription structure has led to Non-value-add commercials instead of decent dev-team leadership
We’re happy to announce the release of Advanced Time Trigger app that solves this issue. With new triggers you can create automations that trigger on/before/after date and TIME saved in date column!