6 docs tagged with "work items"

Work items are the individual units of work inside a PPM project. This guide shows you how to create each type.

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 nested using the parentworkitem_id field to create a tree structure. This guide explains the hierarchy rules, how to set parent–child relationships, and what protections are in place.

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.

PPM lets you plan, track, and deliver projects inside Raytio. You can create projects, break work down into epics, issues, tasks, bugs, and sub-tasks, organise them into milestones, and assign team members.

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.