21 docs tagged with "ppm"

Each work item can have multiple people assigned to it in different roles. This guide shows you how to add, update, and remove assignments.

A project plan is a living document — dates shift, work estimates change, and scope evolves. Without a fixed reference point, it is impossible to answer the question: "How does our current plan compare to what we originally committed to?"

Every project has metadata that doesn't fit into predefined fields. Cost centres, risk ratings, compliance classifications, custom priority schemes — these vary by organisation and even by project. Raytio PPM handles this through categories and custom attributes, a structured extension mechanism that lets you add typed fields to work items without changing the schema.

Every work item has an activity stream that records comments, status changes, and other events. This guide explains how to post comments, read activities, and understand the immutability rules.

This guide walks you through creating a PPM project and moving it through its lifecycle statuses.

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

Project schedules are built from relationships between work items. These relationships — called dependencies — control the logical order in which work can happen. Raytio PPM supports the four standard dependency types along with lead and lag modifiers.

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 module provides two ways to classify work items: labels and categories. They serve different purposes and operate at different scopes. This page explains the distinction.

Raytio PPM stores all the data you need to plan and track a schedule — dates, work, duration, dependencies, and progress — as independent fields. These fields are user-managed: changing one value does not automatically recalculate the others. This page explains what PPM provides and how the pieces fit together.

PPM work items can reference issues in external systems such as GitLab using the externalref and externalurl fields. This is useful for cross-repo tracking when the actual code work happens in a separate GitLab project.

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.

Raytio PPM tracks progress through two complementary mechanisms: manual percent complete on individual work items, and weighted rollup through a database view that computes progress for parent items from their children.

Milestones let you group work items into time-boxed iterations (sprints), releases, or project phases. This guide covers creating milestones, assigning work items, and tracking progress.

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.

The PPM module uses a layered role system that combines tenant-level permissions with project-level roles. This page explains how the roles relate to each other and what each role can do.

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.

A Project is the top-level organisational unit in the PPM module. Work items can be grouped under a project, though this is optional — standalone and cross-project work items are also supported. Each project carries its own metadata, membership, and configuration.

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.

Some work items contain sensitive information — security vulnerabilities, personnel matters, or pre-announcement features — that should only be visible to specific people, even within a project team. The PPM module handles this with a confidential flag on each work item.

Accurate project planning depends on distinguishing three related but independent concepts: work, duration, and elapsed time. Raytio PPM stores all three as independent fields, giving you the flexibility to model schedules precisely.