By 
If a Notion chart shows parent tasks but leaves out their subtasks, start with the database’s sub-item display. Notion recommends showing all items as a Flattened list when sub-items or sub-tasks are missing from a chart. Open the database settings, choose More settings → Sub-items or Sub-tasks, and change Show as to Flattened list.
Then check one named subtask in the chart’s drilldown. A total that looks too low is only a clue: filters, hidden categories, and the selected metric can produce a different number even when the records are present. I recommend tracing a single task before trying to make two totals match.
Follow one missing subtask
Choose a subtask you can identify by its title. Open it in the source database and note its parent, status, date, and any property the chart uses. Confirm that the chart draws from that same source. A dashboard containing several task databases can make two similar-looking views easy to confuse.
A linked view can display the original records while using different filters or groups. If you are unsure whether you are looking at a copy, the guide to editing a linked Notion database explains which changes reach the source. Avoid copying the missing task into another database as a first fix; that introduces another record to reconcile.
If you cannot open the subtask itself, resolve that access question before diagnosing the chart. Notion documents that database and individual-page permissions can restrict which sub-items you can view. A task visible to an owner is not proof that every client or teammate can see it.
Show sub-items as a flattened list
Use the database that supplies the chart. Note the existing display setting first, especially if teammates rely on its nested task layout.
- Open the settings menu at the top of the database.
- Select More settings → Sub-items or Sub-tasks.
- Next to Show as, select Flattened list.
- Return to the chart, click the category that should contain your named subtask, and look for it in the drilldown.
The separate sub-item guide calls the display dropdown Display options and explains that a flattened list shows parents and sub-items as separate entries. Use the label present in your menu; the setting you need is Flattened list.
After the change, inspect the views your team relies on. Notion documents different sub-item display options for different view types, and each database view has its own settings. So check the source view and the chart; don’t assume every view now shows the hierarchy the same way.
Once the named subtask shows up in the chart’s drilldown, the inclusion problem is resolved. Don’t touch that record even if the total still looks wrong; move on to the metric and reporting-scope checks instead. When the subtask is still absent but you can open its page, compare its own property values with the chart’s filters and hidden groups next.
Check what the chart is allowed to show
Work through the chart settings below and change one at a time, so you can tell which condition excluded the named subtask.
Filters and hidden groups
Open the chart’s settings and inspect View settings → Filter. Compare the named subtask’s own values with each rule. Notion’s database filters show only items matching their criteria; an unfiltered table and a chart limited to one client or date range are answering different questions.
Next, inspect Visible groups and Hidden groups in the chart configuration. A completed task can be present in the database but excluded because its status category is hidden. For bar and line charts, these controls sit in the X-axis configuration; for donut charts, they sit under Data. Clicking a category in a chart legend can also hide that group from the chart.
If the chart sits inside a native Dashboard view, check its global filters too. They affect widgets whose underlying views include the filtered property. Two widgets on the same dashboard can therefore have different effective filters. This check is unnecessary for an ordinary standalone chart.
The metric and date buckets
For a bar or line chart intended to count tasks, inspect Y axis → What to show. Choose Count when the question is how many items belong to each X-axis category. A chart measuring another property is not a record count. Notion’s axis settings distinguish the selected property from Count.
If the chart uses dates, inspect Cumulative when that option is available. Notion shows it for Count or Sum with an ascending X-axis. A cumulative series adds earlier values to later points; it should not be compared with a table containing only that day’s tasks. Turn it off when you want the individual period’s value.
On a chart with many categories, the documented limit of 200 groups and 50 subgroups displayed at a time starts to matter. It caps categories, such as days on an axis; it doesn’t mean charts accept only 200 task records. If your chart spans more categories, narrow the relevant date range or scope and compare that same subset.
Decide whether parents belong in the total
Finding the missing subtasks does not settle what your report should count. A flattened list includes parents and children. Consider this educational three-page dataset:
| Task page | Role | Status |
|---|---|---|
| Prepare proposal | Parent | In progress |
| Write brief | Subtask of Prepare proposal | Done |
| Review draft | Subtask of Prepare proposal | In progress |
If all three pages are included and the bar chart uses Status on the X-axis and Count on the Y-axis, the expected category counts are In progress: 2 and Done: 1. The In progress drilldown should contain Prepare proposal and Review draft. The Done drilldown should contain Write brief. This is a count of three pages, not two subtasks; the parent contributes one item. The documented Count metric counts items associated with the X-axis category.
Hide Done in this example and the remaining bar contains two In progress pages, even though all three pages still exist. When your reporting question is “How many subtasks are complete?”, compare against a child-only scope, not the parent’s progress. Don’t force the source records to fit a total until you’ve decided what one counted item represents.
Define the reporting unit before accepting the number: all task pages, parent-level deliverables, or individual subtasks. Inspect the chart’s drilldown to see which pages contribute to the category. Notion’s chart drilldowns open as table views, so you can check the actual titles instead of guessing from bar height. Keep the table used for comparison on the same filters and reporting scope.
For the comparison table, Notion documents Parents only, Parents and sub-items, and Sub-items only under the sub-item filter options for table, list, and timeline views. Those options are specific to the supported view types; don’t assume every chart or board exposes the same controls. I wouldn’t benchmark a chart that’s meant to include subtasks against a parents-only table, because that table leaves the subtasks out.
When the record is still missing
Keep the underlying task pages intact. Chart view does not let you edit database entries directly; to change a task’s properties, open its page or use another editable database view. Deleting a parent is especially risky: Notion says its sub-items are deleted with it.
If the documented display change and the chart checks do not explain the result, record the source database, named missing page, chart type, axis or data properties, filters, hidden groups, and sub-item display setting. Include whether you can open the page and whether another viewer sees it. That gives support a specific discrepancy to investigate without rebuilding the tracker.
If the task is missing from the comparison table as well, continue with the filtered-view troubleshooting guide. The next question is which rule or access condition hides the record, rather than how the chart draws it.
