You create a task for a new project, but Project already contains an older one. You correct it and the next task arrives with the same assignment.
Inspect the creation template before repeatedly fixing records. A preselected relation can suit a project-specific template and be inappropriate for general intake.
1. Confirm the creation path
Create a fictional task through your normal process. Record the database, chosen template, creation view and Project value before editing. Do not change real assignments to experiment.
The objective is to reproduce the initial value and identify its origin.
2. Open the actual template
Open the dropdown beside New, find the template, open its options and choose Edit. Inspect Project inside the template. Editing a generated task is a different operation.
A fixed relation on a template is intended for records that should connect to the same selected existing page. Check Notion’s template documentation for the underlying behaviour.
3. Decide whether the default is intentional
| Purpose | Appropriate default |
|---|---|
| General task for any project | No fixed project selection |
| Task specifically for Project A | Project A if clearly intentional |
| General recurring administration | Only a deliberate verified assignment |
Name specific templates clearly. Project A — review task conveys a different purpose from New task. Misleading naming can make an intentional default look like a mysterious error.
4. Remove an unintended selection
- Open Project on the general template.
- Remove its preselected project association.
- Keep useful page structure and intentional defaults.
- Leave the editor.
- Create a fictional task explicitly using that template.
- Inspect the initial Project value.
The goal is to remove the fixed assignment, not delete a project or rebuild the relation. If the value is still unexpected, investigate the creation view and other mechanisms that set properties.
5. Compare two contexts
Test the same template from an unfiltered source view and from the project dashboard. Record both initial values. This separates a fixed selection from behaviour associated with creation context; it does not promise every filtered view populates properties identically.
If only one context produces the wrong value, inspect that context before changing the shared template again.
6. Repair older records separately
Changing a starting template does not establish that existing assignments are corrected. Inspect the task context, confirm the intended project, correct its association and check the affected project view.
The wrong-relation guide explains the distinction between a wrong selected page and a relation connected to the wrong source. Read relations versus rollups for the connection model.
7. Check repeating templates
Review continuing assignments before relying on future records. A project-specific default becomes questionable after that project ends. Use the recurring tasks guide for the broader workflow.
Common mistakes
- Editing a generated task instead of the template.
- Removing legitimate fixed relations from specific templates.
- Assuming older records were repaired automatically.
- Testing only inside one dashboard.
Frequently asked questions
Why does every task select the same project?
A fixed template relation is one possible cause. Inspect and test before assuming it is the only cause.
Should all template relations be empty?
No. Fixed relations suit records that must connect to the same existing page.
Does correcting one task fix the template?
No. Inspect the database template separately.
Should I delete the incorrectly selected project?
No. Remove the unintended association or template selection; deletion is a different action.
What if the template is empty but tasks still get a project?
Compare creation contexts and inspect other property-setting mechanisms. The empty template alone does not explain the assignment.
Want this already built?
This guide shows you how to build and check this workflow yourself. For the wider client and project workspace, explore Freelancer CRM and compare its structure with how you work.