You mark a task complete, change its client or move its planned date, and the row disappears. Before creating another task, check whether the edit changed the properties that decide where the original appears.
A focused view is useful precisely because it excludes work that does not belong there. The goal is to find the original record and establish whether it left the view intentionally.
1. Find the original task first
Open the task’s original data source and use a Table view without filters for diagnosis. Clear any view search, show the relevant properties and look for the exact task name. If the table is grouped, check collapsed groups as well.
If you still have the task open in a side peek or another tab, keep it open while inspecting its properties. Finding the same page in the source confirms that the record still exists. Avoid copying it into a replacement database.
If you cannot find it, verify that you opened the correct source and can access it. Actual deletion is a separate possibility: inspect Trash if the record is missing from an accessible source, rather than assuming every missing row is a filter issue.
2. Compare the edit with every filter condition
Open the affected view’s settings and inspect Filter. Write the rule as a sentence: “Show unfinished tasks for Client A.” Then compare the record’s current properties with that rule.
| View rule | Edit | Expected result |
|---|---|---|
| Done is unchecked | Check Done | Task leaves the unfinished view |
| Client contains Client A | Replace Client A with Client B | Task leaves Client A’s view |
| Planned Date is empty | Assign Planned Date | Task leaves the inbox |
| Priority is High | Change Priority to Normal | Task leaves the priority view |
These outcomes follow from the view rules. Change a property back only if the edit was wrong. If the edit was correct, look for the task in the view where its new state belongs.
With several conditions, inspect the grouping of AND and OR rather than checking each line alone. Use the filter logic guide to make the intended rule explicit.
3. Check movement within the view
A task may still qualify but appear elsewhere. A sort can move a row after you change its date or priority. A board grouped by Status can place the card in another column when you change Status. Expand the relevant group and clear temporary search terms before adjusting the filter.
For a weekly view, check whether the planned date moved outside the displayed week. Do not remove a useful weekly restriction just to keep next month’s work visible. Open the broader task table, or use the weekly planner guide to separate planning from deadlines.
4. Check whether this is a linked view
A linked view can have different filters from another view of the same source. However, editing a task’s properties changes the source record. Another linked view may therefore include or exclude that same task differently after the edit.
Compare the task in the original source with the dashboard view. If you expected an independent copy, review linked databases versus relations before changing the setup. A different display does not create a second task.
5. Run a controlled test
- Create a clearly named test record in the source, such as “View visibility test.”
- Set its properties so it meets every condition in the affected view.
- Confirm that the same record appears in both source and filtered view.
- Change one relevant property, such as Done, without changing anything else.
- Check the expected result in the filtered view and confirm the original still exists in the source.
- Restore the test value to verify that it reappears, then remove the test record when finished.
Use a test record rather than changing a real client deadline to experiment. If several people use the view, test in a separate diagnostic view before saving different filters for everyone.
Make the next move easier to understand
Name views by their eligibility rule: “Unfinished tasks,” “Client A,” or “Unscheduled inbox.” Keep an accessible All tasks view for diagnosis. When work leaves one queue, a clear destination helps distinguish progress from data loss.
Frequently asked questions
Does leaving a filtered view mean the task was deleted?
No. Locate the original record in its data source. A property edit may have made it fail the view’s filter.
Why does checking Done make a task disappear?
A view filtered to Done is unchecked excludes the record after you check Done. Use an unfiltered or completed-work view to find it.
Can an edit in a linked view change the original task?
Yes. A linked view displays source records. Editing a record’s properties changes that record rather than an independent copy.
Should I recreate the missing task?
Find the original first. Check the source, filters, search and groups. Recreating a record that still exists can produce duplicate work.
What if the task is absent from the original source?
Confirm the source and your access, clear diagnostic view restrictions, and check Trash for possible deletion. A filtered-view explanation alone does not establish what happened.
Keep building your workflow
Explore the practical Notion guides for the next problem in your setup. For a wider client workspace, inspect Freelancer CRM and decide whether its structure fits your work before adapting this task workflow.
Reference: Notion view and filter documentation; Notion data source documentation.