I love Coda, now Superhuman Docs, but one of the areas I have disliked most is the Calendar view. It does not feel very professional or robust. Compared to Notion’s calendar view (not referring to their dedicated calendar app), SuperDoc’s calendar view just feels very lacking, and it is something I hardly use. I have recently been using the TickTick pack to send my tasks over to TickTick so that I can properly plan and schedule.
So, in short, I am curious if there are any plans for the Calendar to get an upgrade?
@CmdrFirezone38 I know you mention the alternate calendar resource, but do you have specifics of what you’d like to see in terms of improvements to start using the feature, if it were enabled? We love taking ideas from the community to the product team to see what’s possible, and the more granular, the better.
There are a lot of conversations about the lack of capabilities of calendar view in the community. Although, related to timeline, a lot of what’s discussed here applies to calendar view:
Some very notable issues with calendar view are:
there is no mobile support at all! Currently, nobody can use calendar in coda doc. The closest to this is timeline, but it’s not a calendar and is pretty tough to use anyway (no rotation makes it nearly impossible to use).
lack yearly and schedule view
dependencies don’t respect hours but only days (so basically calendar view is not usable when there are dependancies)
notifications! / reminders
the option to block past dates in both calendar view and date picker
Here is one example of a calendar behaviour which isn’t absolutely standard but should be easier to achieve:
I’m trying to configure a calendar view for tasks so that users only need to update a single date/time column. The idea is that they click once on the date in the calendar, and the task moves, without them having to edit both start and end.
In my table I have a Start column, an End column, and a Duration column. What I want is:
When a user changes the End date/time, the task keeps its original Duration, and the Start is recalculated so the event doesn’t stretch across many days.
For example, if a task is on August 6th from 13:00 to 15:00, and the user changes the End date to August 9th, I want the task to move to August 9th from 13:00 to 15:00. The user should only have to update the End date/time; Duration should stay the same.
At the same time, I also need the opposite behavior when the user resizes the event in the calendar:
If they drag the start earlier or the end later, the Duration column should update to reflect the new length of the event.
After that, if they move the task to another date again (by changing the End date/time), the new Duration should be respected, and the Start should be recalculated from that updated Duration so the event still doesn’t span multiple days.
I tried to solve this with AI columns, having Duration recalculate whenever End changes, and having Start update based on the current Duration and the new End, but I haven’t found a setup that behaves correctly in both cases. In short, I need a task calendar where:
moving a task is done by updating a single date/time column, keeping Duration constant, and
resizing a task in the calendar updates the Duration, and that new Duration is then used for future moves.
I’d really like the ability to display data from multiple tables on one Calendar view.
For our company calendar (we’re an events agency), for example, we have lots of different types that we want to show together – our clients’ events, internal events, team birthdays, paid holidays, etc. Right now in order to do this we have to maintain a table of “Events” that has columns for all of these very different types of events, and separate them with a Type column, and always know to filter by type. We also have to build routines to populate these tables with rows. For example, instead of being able to display birthdays based on a column in our People table, we have to run an automation to create and remove birthdays when new people are added to or leave the team.
It adds a lot of complexity to working with these tables that really should each be their own distinct type.
Funnily enough the thing that I am most excited about App Views for is being able to build a custom calendar so that we can untangle our data’s structure.
