Hey!
At the end of every week we have a meeting to review the work from this week. Look at tasks, open and created projects, completed projects, etc. Wondering if anyone has set this up before and what would make most sense. If anyone has ideas.
Sharing some initial thoughts to bounce off of:
I could set up a “Weeks” database, but then relating everything (project, tasks, etc) to each week i feel like is too much. They are not conceptually related (I think). Its more of a that each one is a filter. I tried making embedded views, but without the relation on the week database it doesn’t let me link to anything. I could make the views outside of it, but then when I edit the filter to be for the week, (which I would also need to do one by one I think, since theres not formula in filters, i.e. dynamic filtering based on things other than relations) then it changes on all the views and it no longer really reflects that last week.
Potentially with autolinking? Set a “Created Week” every time a project is created, and relate to the week relation “Projects created”. Every week update all open projects with the current week number and autolink that to a relation to the week “Open projects”, and the same for when a project is completed. Same with tasks. I feel like this would be a BIT much for this, but I can’t see another way.
I could add the relation, but then just not use it for data, turn of context filter, and make my own filter by week. But this would require me to set those filters on each one manually… not ideal.
OR Last option is to ditch this all together and just have folder of views called “This past week”. Then take a look at those views together every week / embed them as views with the “Past week” filter into the rich text field for the meeting.
Curious to get some thoughts on this. Thanks!
2 Likes
Hey Ron,
i was also thinking about this. I tried the feed view but it is only scoped to a single database. There is no way to show different entities in one view without them being related in some way. However, creating all these relation fields just for this use-case seems to clutter up your database schema way too much.
I think the best way is to have a scheduled automation that iterates over all the relevant databases, queries the entities that have been created or modified in the last week and assembles a “Week-Report” entity in a dedicated database. That would be quite a bit of scripting but it can be done. This is much cleaner than spamming all of your entities with relations to that Week-Report entity 
Cheers,
Ben
Pretty much everything you’re describing should be automated.
My approach would be to make a Week database. You wouldn’t even need to add entries by hand, just add a scheduled job to create a new Week every monday morning. Each week should have a week number which you would use for auto-linking.
While linking a Week database to Task and Project might feel iffy, in practice you’re not linking the Week itself. What you’re making is actually something like “Weekly Summary” (which would be a better name for the DB anyway) which happens to have a week, same as the Task and the Project databases, so it should feel less iffy .
We do something similar where we have a Daily Summary database (per person) which aggregates the worklogs for that Person for their respective day, and shows if they did overtime or if they were on vacation. This is done with auto-linking via the day:
We also have an use case with auto-linking per month, where we have a planned vs actual summary of the time spent, per month and there are 2 auto-linked databases (Capacity Plan and Monthly Summary)
Anyway, back to your use case, after that you could use a formula or maybe an automation to auto-set the week number per Task/Project. The reason I’m thinking that a formula might not be enough, is that you might want to correlate the Task to when it was transitioned to Done, or stuff like that.
Either way, once you have the week number you can use that for auto-linking which from our experience works very nicely.
1 Like
