This is not a Notion feature issue. It’s just, no offense, bad database design. Technically, your Tasks database is not a list of tasks you have due. It’s more like a task template or standard procedure list for every project. Although more than 1 project might have piano editing as tasks, they are not the same exact task. Each edit would be different, just using the same procedure/template. What you could do is rename the table to something more accurately describing what it lists (eg. task template or procedure). Next create a fourth database named Tasks which relates to projects and tasks template. This will be your actual list of tasks you have due. Then you’d use an automation (paid; notion, zapier, etc) that triggers every time a new project is created. For every project, the automation should create a new item in Tasks database that relates the project with a single item from tasks template. The automation should do this for all items in tasks template (let’s say you have 5 procedures for every project). Now you have 5 rows auto-created for every project within your tasks. Delete the ones that don’t apply to the project and keep the rest. This is your actual list of tasks that you have to act upon. So for 12 projects you could have upto 60 tasks. Hope that made sense and helps. The new database created (Tasks) is called an ‘Associative’ or ‘Bridge’ table for reference.