Issue tracking with SLA clocks

Program / Client Engagement	Milestone & Sprint Phase	Delivery Principal	Budget / Billable Margin	Capacity Utilization	Delivery Health
Meridian Global ERP RolloutCEDX Issues · Record #1040	Phase 03 · Data Migration	K. Vance · Principal Architect	$680,000 · 44% Margin	● 88.5% Billable Util	On Schedule
Q4 Core Kernel Release v4.8CEDX Issues · Record #1041	Sprint 22 · 64 Story Points	A. Rostova · Staff Eng Lead	18 Engineers Allocated	● 92.0% Sprint Velocity	Zero Blockers
Harbor Retail POS DeploymentCEDX Issues · Record #1042	180 Stores · Wave 2 Cutover	M. Okafor · Program Dir	$510,000 · 41% Margin	● 85.2% Field Capacity	Milestone Billed
SOC-2 & ISO Continuous AuditCEDX Issues · Record #1043	Control Evidence Automation	R. Lin · Security PMO	$140,000 Internal Cap	● 100% Evidence Linked	Audit Ready

CORE CAPABILITIES · CEDX ISSUES

Three architectural jobs CEDX Issues gets right on one record.

Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.

01 · PROJECTS & DELIVERY FOUNDATION

Triage is a decision, with a name on it

Nine items wait in the intake queue; a named person is on duty: Ravi, week 32, incident-first rotation. Each row arrives with a suggested component, owner and confidence, and duplicates are flagged at title similarity ≥ 30% before they enter the queue.

02 · LIVE EXECUTION

Workflows with named transitions

Four workflows (Standard delivery, Bug lifecycle, Incident path, Support SLA) with states and named transitions, not a free-for-all: Start, Submit review, Block, Unblock, Accept, Request changes, Quick close. 198 issues ride the default; the Support SLA workflow sits at zero and shows it.

CEDX Issues Live Telemetry ● 320 issues in the workspace

03 · DETERMINISTIC GOVERNANCE

The clocks are on the record

SLA attainment reads 88% with the 25 breached clocks listed individually: issue key and hours over. Cycle outliers get a z-score: CHK-2401 at z=4.44, eight days against a two-day baseline, P0 bug, in progress.

04 · VERIFIED DEMO DATASET METRICS

What the live CEDX Issues build looks like when you open /app/issues.

Every figure below is directly inspectable in the running CEDX Issues application workspace with zero synthetic projections.

ISSUES IN THE WORKSPACE

320

206 open · 114 done

SLA CLOCKS BREACHED

25

of the open clocks, listed row by

WORST CYCLE OUTLIER

z=4.44

8d against a 2d baseline · P0 bug

TOP DEPENDENCY RISK

98

blocks 1 · depth 5 · in progress

4-SCREEN RUNNING BUILD TOUR

Four screens captured from issues.cedxsystems.com, in the order operators run them.

Click any screen below to inspect how CEDX Issues moves from initial intake to verified cross-estate completion.

01 OVERVIEW

The queue, with its health score

Queue health reads 78% and shows the components: SLA attainment 88%, 25 breached clocks, 148 nodes at high dependency risk, 169 cycle outliers. The alerts are root-caused (symptom, cause, fix) and the worst row is named twice: CHK-2401, dep risk 98 and a cycle outlier at z=4.44.

02 TRIAGE

Nine items, one human on duty

The intake queue suggests routing from component ownership (checkout, core platform, inventory, data plane, mobile app) and prints its confidence. The person on duty accepts, re-routes or defers; nothing auto-commits to the backlog.

03 LABELS

A catalog, not a pile of tags

Twenty-four labels, each with a description: p0-watch is the leadership-watched stream, blocked means external or internal wait, compliance covers audit, retention and policy. Open and total counts sit on every row, and the unused-label count is zero.

04 WORKFLOWS

States and transitions you can read

Standard delivery runs Story, Task and Spike through Open, In Progress, In Review, Blocked and Done: 32, 42, 40, 13 and 71 issues respectively. The transitions are named for the human action: Block, Unblock, Request changes, Quick close.

01 OVERVIEW · ISSUES.CEDXSYSTEMS.COM

The queue, with its health score

● Live Screen Capture

Queue health reads 78% and shows the components: SLA attainment 88%, 25 breached clocks, 148 nodes at high dependency risk, 169 cycle outliers. The alerts are root-caused (symptom, cause, fix) and the worst row is named twice: CHK-2401, dep risk 98 and a cycle outlier at z=4.44.

✓ Opened vs resolved, weekly W1-W12Verified in /app/issues

✓ 18 blocked across the workspace, above the 4-week medianVerified in /app/issues

✓ Two P0s in review flagged “protect review SLA”Verified in /app/issues

OPERATOR WORKSPACES · WHO RUNS CEDX ISSUES

Three roles open CEDX Issues every day. Each sees the exact surface they own.

Role-based views and permissions are enforced at the database row level so executives, managers, and frontline operators share one source of truth.

Triage on duty

Works the intake queue on rotation: nine rows, each with a suggested route and a confidence, and a decision to accept, route or defer before the backlog sees it.

● in queue · 9

Quality and docs

Owns the labels catalog and the workflows: 24 labels with descriptions, zero unused, and transitions named so a new engineer reads them without a walkthrough.

● labels · 24 catalogued

Engineering lead

Watches the clocks: 25 breached SLA rows and the z=4.44 outlier are the stand-up agenda, not a monthly report.

● SLA attainment · 88%

ONE CANONICAL RECORD ACROSS 132 APPLICATIONS

Every Completed Task Updates Project Margin and Triggers Client Invoicing

CEDX Issues is not an isolated point tool. It reads and writes the exact same customer, ledger, and identity records as the rest of the CEDX software estate.

CONNECTED MODULE 01 Open /sprints/ ->

CEDX Sprints

A committed issue is scored in the sprint's risk queue with its top signal: the same row, read for planning.

CONNECTED MODULE 02 Open /projects/ ->

CEDX Projects

The board's 340 issues and 32 blocked are this queue's rows, grouped for delivery rather than for intake.

CONNECTED MODULE 03 Open /desk/ ->

CEDX Desk

The support reports in the intake queue (double-charges, login loops) arrive from Desk conversations, with the customer thread attached.

CONNECTED MODULE 04 Open /test/ ->

CEDX Test

A fix that ships is a change that gets verified; the issue's lifecycle continues into the test run, not into a copy of itself.

ARCHITECTURAL PROOF · OPERATOR PERSPECTIVES

Why enterprise operators replace stitched SaaS stacks with CEDX Issues.

"Having identity, least-privilege access, audit trails, and business applications on one kernel cut our security review and provisioning time by 82%."

Sarah Lindqvist

Chief Information Security Officer · Atlas Corp

"We started with one application to fix our most painful bottleneck, and added five more modules on the same login without a single migration project."

Arjun Patel

SVP of Global Operations · Keystone Logistics

"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation from two days to twelve minutes."

Marcus Vance

Chief Revenue Officer · Meridian Systems

LIVE TCO & CONSOLIDATION MODEL · PROJECTS & DELIVERY

Stop paying five vendors to re-sync the same projects & delivery record.

Drag the seat slider to compare your current stitched stack (Jira Align + Kantata (Mavenlink) + Asana Enterprise + Float + Tempo) against running CEDX Issues natively on the unified CEDX estate.

Organization Seats 250 seats

25 seats 500 seats 1,250 seats 2,500 seats

Legacy Stitched Stack

Jira Align + Kantata (Mavenlink) + Asana Enterprise + Float + Tempo

$1,380,000 / yr

CEDX Issues + Full Estate Bundle
All 132 applications · Canonical Postgres · Unlimited Copilot
$267,000 / yr

TECHNICAL & PROCUREMENT FAQ · CEDX ISSUES

Questions operators and architecture teams ask before piloting CEDX Issues.

01 Is the software on this page real? +

Yes. Every screenshot is a capture of the running build and you can open the same build at /app/issues . It runs on demo data.

02 How does triage routing work? +

From component ownership. Each intake row suggests a component and owner with a confidence score (94% on the top row, 61% near the bottom), and the person on duty decides. Duplicates are flagged by title similarity, with the percentage shown.

03 What is a cycle outlier? +

An issue whose cycle time is far off its baseline, scored as a z-value. CHK-2401 reads z=4.44 (eight days against a two-day baseline for a P0 bug), and the alert names the issue, the score and the baseline.

04 What does dependency risk measure? +

Where an issue sits in the blocking graph. CHK-2401 scores 98 because it blocks one issue at depth 5 while in progress; 148 nodes in the workspace sit at high risk by the same measure.

05 Can workflows differ per issue type? +

Yes. The demo workspace runs four: Standard delivery (Story, Task, Spike), Bug lifecycle, Incident path and Support SLA. Each has its own states and named transitions, and the issue counts per workflow are on the screen.

A queue that knows what it owes.

Triage is a decision, with a name on it

Three architectural jobs CEDX Issues gets right on one record.

Triage is a decision, with a name on it

Workflows with named transitions

The clocks are on the record

What the live CEDX Issues build looks like when you open /app/issues.

Four screens captured from issues.cedxsystems.com, in the order operators run them.

The queue, with its health score

How CEDX Issues runs across the week, in the exact order work happens.

Capture & Ingest

Score & Triage

Execute & Approve

Reconcile & Report

Three roles open CEDX Issues every day. Each sees the exact surface they own.

Triage on duty

Quality and docs

Engineering lead

Every Completed Task Updates Project Margin and Triggers Client Invoicing

CEDX Sprints

CEDX Projects

CEDX Desk

CEDX Test

Why enterprise operators replace stitched SaaS stacks with CEDX Issues.

Stop paying five vendors to re-sync the same projects & delivery record.

Questions operators and architecture teams ask before piloting CEDX Issues.

CEDX Issues is running right now. Open it and inspect the record.

Start your 14-day CEDX Issues sandbox.

Start your 14-day sandbox. Instant access to the full revenue estate.