# It is very difficult to make events all day in the events modal (and 00:00 is confusing)

**URL:** <https://meta.discourse.org/t/it-is-very-difficult-to-make-events-all-day-in-the-events-modal-and-00-00-is-confusing/393495>\
**Category:** UX\
**Tags:** events, completed\
**Created:** [January 15, 2026, 12:48am UTC](https://meta.discourse.org/t/it-is-very-difficult-to-make-events-all-day-in-the-events-modal-and-00-00-is-confusing/393495 "2026-01-15T00:48:54Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![nathank](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nathank/32/290039_2.png) [@nathank](https://meta.discourse.org/u/nathank)\
**Post date:** [January 15, 2026, 1:30am UTC](https://meta.discourse.org/t/it-is-very-difficult-to-make-events-all-day-in-the-events-modal-and-00-00-is-confusing/393495/3 "2026-01-15T01:30:54Z")

</div>

Yeah, that flow works quite nicely now that I know it - and understand what `00:00` means / does.

The problem is that this is overlaying a whole heap of meaning on `00:00` which is not obvious or clear to new users. Basically, it needs refinement - or at least ‘just in time’ information.

> [@Lilly](#):
>
> i would expect the date fields in the event modal to behave similar as the insert date function in the composer, but it doesn’t really.

Yes, agree - these really need to work exactly the same.

---

_[View the full topic](https://meta.discourse.org/t/it-is-very-difficult-to-make-events-all-day-in-the-events-modal-and-00-00-is-confusing/393495)._