Totally agree with entering a duration without a date. That’s been on my wishlist for ages but I got pretty dejected seeing no progress in events/calendars in general. Given that it’s just a little nub of text within the item, it seems like it’d be super easy to let us just enter !1.5h and accept that, retain it, and honor it when subsequently adding an actual date (or dragging to the calendar). This is one of those times in Legend where you feel really impressed with the features the app has, then you go to do something that seems perfectly easy and natural …. and nothing. Boo.
Being able to roll up the durations to a parent would of course be incredible – also being able to drag/drop that parent and have all its children splash out on the calendar in sequence – but this quickly snowballs into full-on project management with dependencies, gantting, etc. All of which would be stellar to have, and I think would fit into Legend very well – but which seems lightyears away from where we are today. This too is on my wishlist, but it’s firmly parked in the “pipe dream” category of things I never expect to actually happen. And simply being able to pre-assign durations is very valuable to me even without all that.
The big reason is that when it comes to scheduling, I think many of us are guilty of deciding what we “want” to get done and then “scheduling” it to fit what we’ve already (incorrectly) decided we “should be able to get done tomorrow”. By allowing us to honestly evaluate how long a task will take and ‘assign’ that, we see the huge blocks appear on our calendar as we’re trying to fit them all into a single day. That would be a tremendous help to prevent over-scheduling.
One small part of the “muti-field capability” request, however, would open up a tremendous amount options for many users without turning into a nasty rabbit-hole: access to item properties such as create-date, revised-date, complete-date, etc. This has already been mentioned several places both here and back on Slack.
