Chart View
The Chart view turns your rows into a bar, line or pie chart — counting how many rows fall into each group, or adding up a number property across them. Use it for status breakdowns, pipeline totals, workload by owner, and any question you'd otherwise answer by counting rows by hand.
Creating a Chart View
- Click the + next to the view tabs
- Select Chart
- Choose a chart type, a group by property, and what to measure
The chart stays blank until you pick a group-by property — there's no default, because guessing the wrong one produces a convincing but meaningless chart.
Configuration
All four controls sit in the chart's toolbar:
| Setting | Options |
|---|---|
| Chart type | Bar, Line, or Pie |
| Group by | The property that forms the categories (the X axis, or the pie slices) |
| Measure | Count — how many rows in each group, or Sum — the total of a number property |
| Number property | Which number to add up; only shown when Measure is Sum |
What Can Be Charted
Not every property can be grouped or summed:
| Role | Eligible property types |
|---|---|
| Group by | Select, Multi-select, Status, Text, Person |
| Sum | Number only |
Date, checkbox, formula and relation properties don't appear in the group-by list.
How Rows Are Counted
A few behaviours are worth knowing, because they change what the numbers mean:
| Situation | What happens |
|---|---|
| A row has no value for the group-by property | It's grouped under Untitled rather than dropped |
| A multi-select row has several values | It's counted once in each group — so the totals across groups can exceed your row count |
| Sum with an empty number | Treated as 0 |
That second one is the common surprise. If a task is tagged both Design and Research, a count grouped by tags adds one to each.
Filtering and Search
The chart is built from the rows that pass the view's filters and the search box — not the whole database. Narrow the filters and the chart redraws immediately.
This makes filters the main tool for slicing: filter to one client, one quarter or one owner, and the same chart answers a different question.
Examples
| Question | Chart | Group by | Measure |
|---|---|---|---|
| How much work is in each stage? | Bar | Status | Count |
| What's the value of the pipeline by stage? | Bar | Stage | Sum of Amount |
| Who's carrying the most tasks? | Bar | Owner | Count |
| How does the workload split by type? | Pie | Category | Count |
Sharing
Chart views render on share links and embeds. On a view-only link the chart displays but its configuration controls are disabled, so recipients can't change what's being measured.
Best Practices
| Do | Avoid |
|---|---|
| Pick the group-by property deliberately | Leaving it unset and assuming the chart is empty because of a bug |
| Use filters to scope the question | Charting the whole database when you mean one client or quarter |
| Use Pie for a handful of categories | Pie charts with a dozen thin slices — use Bar |
| Remember multi-select double-counts | Reading a multi-select total as a row count |
Troubleshooting
| Problem | Solution |
|---|---|
| The chart is blank | No group-by property is selected — pick one |
| A property is missing from Group by | Only Select, Multi-select, Status, Text and Person can be grouped |
| Sum is unavailable | Sum needs a Number property; add one, or use Count |
| An Untitled bar appears | Those rows have no value for the group-by property |
| Group totals exceed the row count | The group-by property is multi-select, so rows count once per value |
| The numbers look too low | A filter or the search box is narrowing the rows — the chart only sees what the view sees |
Related
- Views, Filters & Sorting
- Property Types — Select, Status and Number configuration
- Dashboards — Charts across multiple databases
- Timeline (Gantt) View