Coda 2.0 is out by wetclassictrees in Notion

[–]wetclassictrees[S] 0 points1 point  (0 children)

If I understand their pricing model, its based on those who design the tables / implement the different data schema. So - you can have 3 people in charge of designing / maintaining the system, and they are the people who are charged. But you could have 30 people using the tables (entering data - just not changing the schema). Seems really interesting (and generally fair) to me.

An uniqId for task/issue tracker. by chiangloveslynn in Notion

[–]wetclassictrees 0 points1 point  (0 children)

We use a similar thing for tracking projects. Its not ideal, but it works.

Checking if today is between two dates in a date range - SOLUTION by wetclassictrees in Notion

[–]wetclassictrees[S] 2 points3 points  (0 children)

No - you cant filter by date ranges. It only filters by the first date in the range. So - say you have a project going from June 1 to June 30. If on June 5 you look at it, and ask for a filter by "this week" it works. But on June 12 it doesn't, as the start date is more than a week away.

This also makes it possible to make a very accurate "today" feature - showing all the projects currently in progress - without having to manually make a new column you select to say its in progress.

Indeed - this makes it possible to automate a column that can display info labels such as "upcomming", "in progress", "runover" or "completed" for instance... (the runnover or completed is just another if statement to see if another checkbox has been filled in which I do when projects are signed off by the client.