If a task opens from its direct URL but is missing from one Notion view, compare that view's filters with the task's actual property values. The task can still sit in its data source while a board, list, or calendar leaves it out. Notion gives each database view its own settings, so a task that shows up in one view isn't guaranteed to show up in another.
I would locate the exact task before changing anything. That avoids recreating a record that still exists or changing its status merely to satisfy the wrong view. These checks cover database views inside Notion.
Locate the task and its data source
Open the task's direct URL using the same account that sees the empty view. If you do not have the URL, ask a collaborator who can see the task to copy it. The result determines your next check:
| Result | Next check |
|---|---|
| The task opens, but one view omits it | Compare that view's source, filters, and display settings with the task. |
| The task opens, but you cannot find it in the database you expected | Confirm the task's actual data source. Similarly named databases can contain different records. |
| The task URL reports No access | Ask the owner to inspect access to the task and its source. A broader filter will not grant permission. |
For a linked view on a dashboard, open the database's settings and select Manage data sources. Check the entries under Sources and Linked against the database containing your task. Notion's data-source instructions distinguish locally held sources from linked sources. Confirm identity before comparing two views with similar names.
If you have permission to manage views, use a separate diagnostic Table view of that same source. Add a view with + beside the existing views, or through the current view’s name and New view on smaller screens. Select Table and name it “Task diagnosis.” Keep the operational view’s rules intact while you inspect the task.
- In Task diagnosis, open settings → Filter under View settings. Inspect any conditions; if you need to remove one from this diagnostic view, open it and choose ••• → Delete filter.
- Check Group and reveal hidden groups, or choose Remove grouping in this diagnostic view. Clear any database search query.
- Locate the record and compare its direct URL with the task you started from. If you search temporarily, clear that query before judging the full view again.
Those filter and group controls change only the diagnostic view, so the team’s working selection stays as it is. If this account can open the task but can't find it in that same source, pause and recheck source identity and the archive/sub-item states below. Creating a replacement task would hide the discrepancy.
Database search matches page titles and properties, so search for a stored task name or property value, not a sentence from the page body. An active query restricts the displayed records.
If the task page has an Archived banner, check that state separately. Notion's Archive feature is currently a Business and Enterprise beta; archived database pages are filtered out of views and can be inspected through database settings → View archived pages. Its archive instructions explain that the page still exists. Decide whether the task should remain archived before changing a normal filter.
Compare the filter with the record
Open the affected view's settings, then select Filter under View settings. Notion's filter controls use property values to include or exclude records. Inspect the entire rule, including any advanced groups.
Read each condition against the task you located. For a positive condition such as Status is In progress, a task marked Not started doesn't qualify. A rule that requires a particular assignee excludes an unassigned task, and one that requires today's due date excludes an empty Due field. When that happens, inspect the record; don't fill it with invented values.
Check the property the rule names, too. A project can have a deadline while its task's Due property is empty. The filter reads the task property you selected, and the project's deadline won't fill that value unless the task itself has it through the appropriate property.
Advanced filters combine AND and OR, and you can nest groups up to three layers deep. To inspect or build the grouped rule, use settings → Filter under View settings → Add advanced filter. Expand the groups before you decide the task should appear. Here's an illustrative rule for a task view, written in plain words. Build it with those controls rather than pasting it as a formula:
The assignee includes Alex, AND either the status is In progress OR the due date is 26 October 2026.
The table below uses an exact-date condition, so you can see at a glance which sample tasks belong and which drop out.
| Task | Assignee | Status | Due | Matches? |
|---|---|---|---|---|
| Draft homepage | Alex | In progress | 2 Nov 2026 | Yes: Alex and the status branch match. |
| Request logo | Alex | Not started | 26 Oct 2026 | Yes: Alex and the due-date branch match. |
| Clarify scope | Alex | Not started | Empty | No: neither OR branch matches. |
| Review copy | Sam | In progress | 26 Oct 2026 | No: the outside assignee condition fails. |
This follows the documented AND/OR filter-group logic. To show all of Alex’s tasks plus anything due on 26 October, you would need a different rule: the assignee includes Alex OR the due date is 26 October 2026. Write the intended selection in plain language before changing the group structure.
Choose the record change or view change
Once you find the failed condition, decide which value is wrong. If the task was assigned to the wrong person, correct the task. If the board is meant to include unassigned work, change its rule. Changing a truthful task value merely to make it appear on one board creates misleading data everywhere else.
The distinction matters in a linked view. Notion says edits to linked source pages or property values affect the original source, while views, filters, sorts, and groups created in the linked database do not change the original database's views. A view adjustment and a record edit have different scopes.
If a colleague sees the task in the same view and you don't, check your personal filter state before assuming permissions changed. Notion's personal versus shared filter behavior works like this: choose Save for everyone and the filter applies to everyone using the view; leave that option unselected and it applies only to you.
Keep shared changes deliberate. Record the existing rule, adjust the smallest incorrect condition, and use Save for everyone only when the new selection is appropriate for the team. Notion's Can edit content permission allows record editing without control of the original database's views, filters, or sorts. It still lets users create linked databases and edit their views, filters, and sorts. Ask the view's owner for help when your actual permissions prevent the adjustment.
Check sub-items and display settings
If the missing task is a sub-item, a matching property value may still be insufficient. Open the view's settings → Sub-items and inspect both Display options and Filter options or Include. These settings affect the filtered result, as Notion's sub-item instructions explain.
Table, list, and timeline views support a nested display or a flattened list. Their filter choices include Parents only, Parents and sub-items, and Sub-items only. Check whether the rule is selecting the parent, the child, or both; open a parent's toggle when inspecting a nested display.
Board, calendar, and gallery views have different display choices: Card property or Flattened list. Notion's sub-item docs list Parents only as their one filter option. So a child that matches your due-date rule doesn't mean its parent qualifies for that view. I'd open a diagnostic Table view to inspect child-level matching, because not every layout offers the same sub-item filters.
For ordinary tasks, inspect Group in the view's settings. Groups can be explicitly hidden, so a task may be in a hidden group even when its filter conditions are correct. Sorting changes the order of records; it can put the task farther down the view, but it does not provide an exclusion condition. Notion documents these separate group and sort controls.
If the discrepancy occurs only in a calendar view, inspect the Date property that calendar displays. The calendar layout uses a Date property; a correct status filter alone does not establish that you are looking at the task's intended date. The database-view selection guide explains the different questions each layout answers.
Verify the result without expanding access
Return to the original view after the targeted change. Confirm that the task appears and inspect another record that should remain excluded. Reopen the task itself to confirm that its assignee, status, and date still describe the real work. If you changed a shared filter, have a collaborator check that same view.
For the example rule, suppose Clarify scope was correctly assigned to Alex, still Not started, and genuinely had no date. If that view is meant for active or specifically dated work, its exclusion is expected: use an appropriate unfinished-work review view. If the view is meant to include every task assigned to Alex, fix the selection rule instead of making up a due date. After that change, Clarify scope should qualify; Sam’s Review copy should stay excluded by an Alex-only rule. Apply the same logic check to the rule you intended for your Notion view.
A client who cannot open the task URL needs an access check, even if you can see the task. Ordinary filters control display; they do not create a privacy boundary. On Business and Enterprise, Notion's page-level access rules apply across views, including linked views. Changing a presentation rule does not repair a missing grant of access.
Ask the owner to inspect the task's sharing and the source's access rules for the affected person. Keep any client change within that client's intended scope; the client portal permissions guide covers that check. If the task's URL opens but the correct view still omits it after these checks, give the owner the task URL, data-source identity, full filter rule, and sub-item settings. That evidence is more useful than replacing the task or removing every shared filter.
