And having the ability to control that is crucial. If you define the weekend as Friday-Saturday, you can quickly turn that on. For this to work at enterprise level, the standard work week option should be there.
Example: I hire 4 people who would work 5 days each for a project, schedule them. Then, the schedule changes. Instead of from Monday to Friday, it will be from Wednesday to next Tuesday. In TeamGantt, you simply scrub all their bars forward and because Sat-Sun are omitted, that’s all you do. In coda, it means you have to split up the task into 2 to omit the weekend.
Here’s the thing: Coda is not a project management tool.
It is a no code tool with a rich development environment, containing the Coda Formula Language and the Pack development environment.
It is used to build
- collaborative writing and design surfaces
- team hubs (wikis)
- no code applications
- multi use AI
And yes, some people, including me, use it to do task list management. This can range from simple task lists, to relatively complicated project management, including a Gantt like time line view.
It could be that Coda is already working on something like this, I don’t know.
But if they did they would need to take the following into account:
- as @Christiaan_Huizer pointed out, different definitions of weekend in different countries and cultures;
- as you pointed out, changes in the definition of what a weekend is for company specific purposes;
- public holidays. (And here in the USA, the distinction between federal and state public holidays).
– this leads to a factory/ working calendar.
- further, this impacts on dependencies, in many different ways
For Coda to develop polymorphic functionality to do this will be orders of magnitude more complicated than what it would be for a maker to build requirement specific solutions.
I’m not a programmer so I would take your word for it. I would argue that Coda, for me, is the best project management platform I have tried over Monday, Airtable, or whatever because of its ability to link all things you listed out Coda is able to build. With relational databases, I can quickly assign a people database to a project database while specifying a product defined, and changed easily using the wiki feature. All done with no code and AI. It’s not yet a robust scheduling tool like TeamGantt but it does everything else well. And unlike Monday, you pay less for Doc Maker, take all the data with you if you stop using Coda because you are not beholden to the app itself.
1 Like
A couple of suggestions for further improvements of timelines:
- When I have a row in a timeline without dates or a duration, it would be great if Coda worked the way Notion does: while hovering over a row without dates, a grayed out block appears on the timeline and you can easily place the block on the timeline thereby setting the start and end dates for the row.
- When adding a new item between other rows on a timeline sorted by date, it would be great if the start date would default to the same date as on the row above… or any other logic that would actually keep the new row in its place in the timeline.
5 Likes
I came here looking for an answer to this same issue. Are there plans to be able to adjust “multi-year” to a user-specified value? Or at least base the multi-year fit on the smallest number of years that will show all data? That would be incredibly helpful.
Much like the example shown by Bradley (Feb. 7th) my data spans 2 years, but the timeline fit view expands to 5 years total. If I try to print to PDF the page to include the timeline in reports/emails/etc. the display extends even further to 10 years total, obscuring the “actual” data through compression. IMO this completely limits the value of the timeline.
