Skip to content

Tree chart

A release, its epics and their tasks.

Definition · Updated Nov 2, 2026

A tree chart branches from one root into levels, such as a release, its epics and their tasks, with a status on each node. Use it for release plans, org charts and any hierarchy with a state per item.

Pay once. Every update included.

Live preview

Release dependenciesRelease v4.2 · Dec 05 depends on 3 epics and 4 tasks; 2 items are blocked and 2 have shipped.RELEASEEPICSTASKSv4.2 · Dec05Billing v3SSO forteamsReferralv2InvoicesSAMLloginSCIMsyncLegalreview
Release dependencies
ItemLevelParentStatus
v4.2 · Dec 05Release–Release
Billing v3Epicsv4.2 · Dec 05Shipped
SSO for teamsEpicsv4.2 · Dec 05In progress
Referral v2Epicsv4.2 · Dec 05Blocked
InvoicesTasksBilling v3Shipped
SAML loginTasksSSO for teamsReview
SCIM syncTasksSSO for teamsTodo
Legal reviewTasksReferral v2Blocked

Sample data: release v4.2 (Dec 05), its epics and their tasks, each with a status colour (shipped, in progress, review, todo, blocked)

Size
Data shape
Nodes with a parent and a status
Good for
Release plans, org charts, hierarchies
Avoid when
Nodes have several parents
Sizes
XS, S, M and L, re-laid out from the data

Anatomy

Inspect it like the Figma file.

The same layers, names and tokens as the component. Select one to read its size, fill and style.

Layers

040 / Tree

chart/040-tree
plot · tree
Layer
link
Type
Vector
Size
28 × 24
Stroke
text/unselected
Group
Marks · 30

Layers

040 / Tree

chart/040-tree
plot · tree
Layer
link
Type
Vector
Size
28 × 20
Stroke
text/unselected
Group
Marks · 22

Sizes

Re-laid out, never scaled.

The same data at XS, S, M and L. Every size is redrawn from the data, so text and line weights never shrink.

M against S

Width360 px480 px

Plot328 px440 px

Labels1119

Marks2230

Height212 px246 px

Same tokens at every size: text styles, 1 px lines and mark radius stay put.

When to use

A hierarchy with states.

Three signs it fits, and three signs another type fits better.

Does each node have one parent?

Links in any direction.

Yes: Keep the tree

Is status the point?

Amounts per level.

Yes: Keep the tree

Is it the plan, not the dates?

Items on a timeline.

Yes: Keep the tree

Code and Figma

One name in Figma and in code.

Every Figma property is a prop with the same name and values. One command installs it.

Figma

chart/040-tree

size
legend
Property = propValuesDefault
size"xs" · "s" · "m" · "l""xs"
legendfalsefalse
color"cat-1" · "cat-2" · "cat-3" · "cat-4""cat-1"
npx shadcn add @chartory/tree
tree.tsx
import { Tree } from "@/components/chartory/tree"import { releasePlan } from "./release-plan"export function ReleasePlan() {  return (    <Tree      data={releasePlan}      size="m"      legend={false}    />  )}

Hearth widget

Tree as a widget.

The chart in a Hearth card with a hero number and two blocks. One token set, light and dark.

Code
Get the code

EmberPreset

ChartoryDefault preset

Pick the blocks, the size and the preset for your own widget.

Read the Hearth widget docs

FAQ

Tree questions.

What people ask before they put a tree in a dashboard.

Something else?

hello@usechartory.com
  • Release, epics and tasks, named along the top in the sample.

Related types

The same question, a different shape of answer. Every type ships in Figma and in code.

Same family

Relationship

17 types in Chartory answer this question.