Skip to main content
Initiatives is the planning layer above projects and issues. Use it when you need to group work at a strategic level — above delivery tracks and individual work items.

​
What initiatives are for

An initiative represents a strategic direction or major outcome. Projects and issues underneath it are the delivery mechanism for that direction. The hierarchy is:
Not all issues need to belong to a project, and not all projects need to belong to an initiative. Add this structure when it is useful, not by default.

​
The tree view

The Initiatives page renders all initiatives as an expandable tree. Root initiatives appear at the top level. Child initiatives are indented beneath their parent. Each row shows:
  • a chevron to expand or collapse children
  • the initiative’s level label
  • the initiative title
  • a status badge
Clicking a row opens the initiative detail page.

​
Initiative fields

Each initiative has:

​
Initiative detail

Opening an initiative shows its title, description, level, and status. Two tabs are available:
  • Sub-Initiatives — child initiatives nested under this one. A Sub Initiative button creates a new child directly from here.
  • Projects — projects linked to this initiative.
The properties panel (accessible via the sliders icon) shows the Assignee, Parent initiative, and other metadata.

​
Nested initiatives

Initiatives can be nested to any depth. A broad strategic direction can contain multiple sub-initiatives, each with their own projects and issues. The tree on the list page reflects this structure and can be collapsed to focus on top-level directions.

​
When to use initiatives versus projects

If work is concrete enough to assign to an agent directly, it belongs in Issues. If it needs a delivery track with a timeline, use Projects. Initiatives are for everything above that.