Skip to main content

Project portfolio management

Epics, issues, dependencies, and baselines with platform-native access control.

Raytio Projects lets organisations plan, track, and deliver work across a portfolio. Epics, issues, tasks, bugs and sub-tasks share a single work-item model, connected through hierarchy, qualitative links, and scheduling dependencies - with immutable baselines so you can measure how the plan has drifted from what was committed.

Capabilities

Unified work items

One model holds all five work-item types, so a single API and consistent behaviour apply across the portfolio. Per-project statuses map to standard categories for reporting.

Three ways to relate work

There are three ways to relate work items to each other, and all three can cross project boundaries.

  • Hierarchy expresses containment - an epic contains issues, an issue contains tasks.
  • Links express qualitative relationships, such as one item blocking or duplicating another.
  • Dependencies drive scheduling, with lead and lag offsets.
Standard dependencies with lead and lag

Finish-start, start-start, finish-finish and start-finish dependencies are supported. Each carries lead and lag offsets, and cycles are detected.

Work, duration and elapsed time kept independent

Effort, working days and calendar dates are stored separately, so real scenarios are modelled faithfully rather than forced into one formula.

Weighted progress rollup

Leaf items carry percent-complete; parents roll up a work-weighted average, with manual override where needed.

Immutable baselines and variance

A baseline snapshots dates, effort, duration, progress, dependencies and milestones. A variance view computes deltas against live data for schedule-health reporting.

Confidential work items

A confidentiality flag hides sensitive items from most members. Only administrators, the assignee, watchers and explicitly granted users can see them.

Structured custom attributes

Project-scoped categories add typed, validated custom fields without schema changes.

Notable details

Interoperates, doesn't re-schedule

There is no auto-cascade and no resource levelling. Values change only when set - by you, or by an external scheduling tool via import and export.

Readable keys

Each item gets a key from the project prefix plus a sequence, for example WEB-42.

Part of Operate · Read the documentation →

Verified customers, protected data, and agents you can hold to account.