Project Structure and Hierarchy

Understand how Organizations, Projects, sections, and work items roll up for navigation and reporting.

Overview

Project structure defines how delivery work is organized inside a Project. A clear hierarchy makes navigation, reporting, and governance easier.

Key Concepts

• Organization → Project: top-level separation of work
• Project sections: grouping mechanism for phases, sprints, and workstreams
• Work items: requirements, tasks, tests, and artifacts
• Hierarchy: parent-child relationships that support rollups

How It’s Used

Use sections to model delivery phases and workstreams. Use consistent naming to support search and reporting.

Benefits

• Faster navigation in large Projects
• Cleaner timelines for Gantt views
• Clearer ownership when sections map to workstreams

Setup Steps

1

Confirm Organization and Project boundaries

Create one Organization per client or department. Create one Project per initiative.

2

Define Project sections

Create top-level sections for phases or workstreams. Add child sections for subphases and sprints.

• Project Sections

3

Standardize fields used for reporting

Add custom fields at Project scope. Use Organization-level Segmentation for cross-Project reporting.

• Project Settings and Configuration
• Segmentation

Best Practices

• Keep section names stable and unique within a Project.
• Use the same phase names across related Projects.
• Keep workstream sections aligned to real ownership boundaries.

Summary

Project hierarchy is built from Organization and Project boundaries plus section structure. Consistent structure improves navigation and reporting.

Related:

• Organizations
• Projects
• Creating and Customizing Gantt Charts