Hierarchy, Links, and Dependencies
Work items can be connected to each other in three distinct ways. Each serves a different purpose, and choosing the right one keeps plans readable and reporting meaningful.
Work items can be connected to each other in three distinct ways. Each serves a different purpose, and choosing the right one keeps plans readable and reporting meaningful.
The PPM data model is built around four core concepts — Projects, Work Items, Milestones, and Baselines — with work items connected to each other through parent–child hierarchy, links, and dependencies. Understanding how these relate is the key to understanding how Raytio's project tracking works.
Raytio's Project Portfolio Management (PPM) module lets organisations plan, track, and deliver work across projects. It brings structured project tracking — epics, issues, tasks, bugs, milestones, and dependencies — directly into the platform, with the same access control and multi-tenancy guarantees as the rest of Raytio.
Rather than having separate tables for epics, issues, tasks, bugs, and sub-tasks, the PPM module stores all of these in a single Work Item table. A type column distinguishes them. This page covers work item types, keys, and statuses. For how work items are connected to each other, see Hierarchy, Links, and Dependencies.