Kodavara Guide

ClickUp WBS Numbering: How to Add 1, 1.1 and 1.1.1 Codes to Tasks

Project teams often need work breakdown structure codes such as 1, 1.2 and 1.2.3 on every task. ClickUp can nest subtasks, but it has no built-in outline or WBS numbering. This guide covers what ClickUp offers and how to keep codes accurate as the tree changes.

Last reviewed October 2026. ClickUp changes often, so check ClickUp's help center for the latest. Written by Kodavara, an independent ClickUp Partner. Not published or endorsed by ClickUp.

What ClickUp Does Today

What You Can Do Natively

Start with the features available on your ClickUp plan.

Nested Subtasks

The Nested Subtasks ClickApp lets subtasks sit inside subtasks. The default is 3 levels and the maximum is 7. A task can hold up to 1,000 subtasks, nested ones included.

Limits Apply Going Forward

Lowering the nesting setting does not change existing nested subtasks. It only blocks new ones beyond the limit.

Custom Task IDs

These give a prefix and a running number per Space, which is not hierarchical. A number such as 1.2.3 cannot be produced this way.

Manual Numbering

Many teams type the numbers into task names or a custom field, which works until tasks are added or moved.

Where It Falls Short

The Gaps People Run Into

If these are your problem, keep reading.

There is no native WBS or outline numbering. A request for hierarchical numbers like 1 and 1.1 has been open on ClickUp's feedback board since 2020.
Typed numbers go stale when tasks are inserted, removed or moved.
Renumbering a large project by hand is slow and error-prone.
Custom Task IDs cannot reflect position in a tree.
Reports and exports cannot sort by a code that was never stored.

Worked Example

Example: A Task Tree and Its WBS Codes

The code is the task's position in the tree. Add a task, and the codes beneath it follow.

Code	Task	Level
1	Design	1
1.1	Concept	2
1.2	Drawings	2
2	Build	1
2.1	Foundations	2
2.1.1	Excavation	3

Sample data for illustration.

How Render WBS Mapper Does It

Set It Up Once

The WBS Mapper works out each task's code from the tree and writes it back to ClickUp.

Connect and Choose a List

Connect ClickUp and create a configuration for the List that holds your project tasks.

Choose Your Format

Pick the numbering style, then where the code is written: a task name template, a custom field, or both.

Preview the Codes

See the exact name and value each task will get before anything is written.

Activate and Add the Trigger

Use a ClickUp automation that calls Render, or let Render check the List on a schedule. New subtasks are numbered under their parent.

Rebuild When You Choose

Renumber the whole List only when you decide to. Render checks the tree again before it writes and stops if it changed after you approved.

See the WBS Mapper Book a Free Consultation

FAQ

Common Questions

Not here? Ask us.

Does ClickUp support WBS numbering?

There is no built-in WBS or outline numbering. Hierarchical numbering is an open request on ClickUp's feedback board.

How many levels can ClickUp nest?

The Nested Subtasks ClickApp defaults to 3 levels and allows up to 7.

Do the codes update when I move a task?

A move in the hierarchy is found by a scheduled scan, because ClickUp does not send an event for it, so it is not instant. A full renumber is a rebuild you preview and approve.

Can I preview before it changes anything?

Yes. The preview uses the same logic as the live run and writes nothing.

Where does the code go?

Into the task name, using a template you control, into a custom field, or both.

Can I find an old code?

Yes. You can search by code, task or title across past renumberings. A code is a position, so it may have belonged to a different task earlier.

Keep Reading