A task can appear in your main database while being absent from its expected project. Before recreating it, inspect the Project relation. The task may exist but have no project connection.
This guide creates a review queue and distinguishes legitimate standalone work from records that need fixing.
1. Confirm Project is a relation
Inspect Project in Tasks. This recipe requires a Relation connected to Projects. A text field with a project name is not that connection. Follow how to connect two databases if necessary.
Keep existing project-name text while checking assignments; it can help identify the intended destination.
2. Create the review view
Add a Table called Project assignment review. Filter Project is empty. Show Task, Project, your completion property and an owner if already tracked.
Start without excluding completed tasks to check history. If you later exclude them, name the view Active tasks without a project so its purpose is explicit.
3. Test three cases
| Task | Project relation | Result |
|---|---|---|
| Review client homepage | Empty | Appears for review |
| Prepare proposal draft | Website proposal | Excluded |
| Update personal workspace notes | Empty | Appears; may be intentionally standalone |
The filter detects a missing connection. It cannot decide whether every task needs a project.
4. Assign the existing project
- Read the task context.
- Confirm the intended project.
- Open Project and select the existing project page.
- Open that page to verify its identity.
- Confirm the task leaves the empty-relation view.
- Check the original in your unfiltered source view.
Leaving the queue means the assignment is repaired, not that the record has been deleted. Do not create a new project because existing names are ambiguous.
5. Keep standalone work intentional
Administrative reminders and one-off personal actions may need no project. Optionally add Task Context as Select with Project work and Standalone work.
Narrow the queue to Project is empty AND Task Context is Project work. Keep a separate view for Task Context is empty so unclassified work still receives review. These are suggested labels, not built-in categories.
Use the AND and OR guide to combine conditions.
6. Check the project display separately
A correct relation does not guarantee eligibility for every dashboard. Inspect filters for completion, owner and date range. Use task visibility troubleshooting before recreating the record.
Common mistakes
- Confusing project-name text with a relation.
- Assigning every standalone task to a fake project.
- Excluding unclassified tasks before reviewing their purpose.
- Creating duplicate tasks instead of repairing the original.
Frequently asked questions
Does every task need a project?
No. Standalone work can intentionally have no project relation. Distinguish it from an assignment you have not reviewed.
Why does a project name appear while the relation is empty?
The name may be stored in separate text. Inspect the actual Project relation.
Why does an assigned task leave this view?
The view shows empty Project relations. Selecting a project makes the record ineligible.
Should completed tasks be included?
Include them for historical assignment review. Exclude them only when checking active work.
Why is the task still missing from its project dashboard?
Check filters and the source. Completion, owner or date conditions may exclude a correctly linked task.
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.