CloudPMO is in pre-launch. Request early access →

Changelog

See what's new in CloudPMO.

Every release of the platform, from the latest timesheet improvements back to the v1.0.0 launch. Want a heads-up when something ships? Join the newsletter at the bottom of this page.

v1.0.2 22 July 2026
Latest

"All my projects" timesheet grid

  • All my projects now shows every project where you have an assigned task, with each project shown once.
  • Projects stay visible during weeks with no scheduled task, offering their assigned out-of-week tasks in a project-specific selector.
  • Each visible task shows daily planned effort, and each project has its own Daily total.
  • Contributors can add only their own assigned tasks to a week; project editors remain limited to tasks assigned to the selected resource.
  • Planned-hours failures can be retried within the affected project card without losing the other project groups.
Release history

Every step since launch

v1.0.1 22 July 2026

Timesheet daily guardrails

Added

  • Task-level planned hours now appear beneath each visible Timesheets input.
  • Daily planned totals exclude hidden, out-of-week, and ticket-linked schedule rows.
  • Accessible over-allocation warnings identify planned hours and resource capacity.
  • A canonical dated ledger stores actual minutes by schedule task or work item and date.
  • Contributors can save time for their linked resource without Planning edit permission.

Improved

  • Timesheet submission now uses one idempotent full-week replacement before workflow submission.
  • Daily actual capacity, weekend approval, target eligibility, and tenant, project, and resource authority are enforced by the API.
  • Submitted and approved weeks are read-only; rejected weeks can be corrected and resubmitted.
  • Loading, empty, error, retry, and responsive states now have automated and visual evidence.

Fixed

  • Retrying the same week no longer adds actual time twice.
  • Hidden task plans no longer inflate the displayed Timesheets total.
  • Replacement and submission or approval decisions now share a database week lock, preventing workflow races.
  • Actual-entry responses no longer expose internal actor, tenant, or persistence metadata.

Known limitations

  • Daily capacity is weekly capacity divided by five; resource-specific calendars are not yet modeled.
  • Capacity is enforced within the selected project, not across all projects.
  • PostgreSQL rollback and serialization tests require a database and are skipped when none is available.
v1.0.0 June 2026

First production-ready release

The launch release delivers the complete project portfolio management feature set across eleven epics.

Platform foundation

  • Tenant-scoped authentication with JWT tokens, six role types, and role-based guards on every route and endpoint.
  • PostgreSQL schema for tenants, users, projects, tasks, and demand, plus the OpenAPI v1 specification.
  • Standard error envelope and correlation IDs on every request for distributed tracing.
  • Accessible app shell: keyboard navigation, light and dark themes, global search, and WCAG 2.1 AA compliance.

PMO workflows

  • Tenant settings, user management, and project creation and archival.
  • Demand intake with validation, four-dimension scoring, weighted prioritization, and approve, reject, or on-hold decisions.
  • Project workspace with Attention, RAID Summary, Milestone Timeline, and Schedule Snapshot panels.
  • Work items with their own status workflow, linkable to schedule tasks and RAID actions.

Planning and scheduling engine

  • Four planning views: Grid, Board, Timeline, and Gantt.
  • Work Breakdown Structure with hierarchical WBS numbers, indent and outdent, and auto or manual scheduling modes.
  • Finish-to-start dependencies, critical path highlighting, named baselines, and variance reporting.
  • CSV export and import with all-or-nothing row validation.
  • RAID register with five item types, four severity levels, optimistic concurrency, and full audit logging.

Known limitations

  • DOCX versions of user-facing guides require pandoc to regenerate; Markdown is authoritative.
  • The development seed endpoint is disabled in production and must not be relied on.
  • Advanced capacity forecasting (burn-down projections, scenario modeling) is planned for v1.1.0.
v0.1.0 June 2026

Developer foundation

The initial developer-focused release. Not intended for end-users.

  • Local Docker runtime foundation for the app layer.
  • Web shell, planning route boundary, and API package boundary.
  • Scheduling Engine API contract coverage and a standalone UI validation surface.
  • In-app help JSON and developer documentation.
See pricing Start free
✓