Thanks for bringing this back to my attention. I can’t really remember if it was I that marked it as resolved or the support team (I never sent them an email about this).
The way I “fixed” it (not really a fix, but a workaround) was to mark it as not required. It’s not really a reliable solution, since there are use cases – probably like yours – that need the time picker to be required. This was sort of not the case here, so that’s how I solved it.
