Repository navigation
Premium Workspace 2026 10 18
The requested project layouts retain the dark ServiceOps sidebar, branding and theme system. Accepted on local MicroK8s Helm 224, version 1.113.50, schema 20261018_0133.
| Area | Implementation and state |
|---|---|
| Summary | Actual weekly metrics, status donut, priorities/types, privacy-aware avatars and activity |
| Timeline | Dense issue/status/start/due columns, recursive hierarchy, derived parent dates, avatar bars, dependency curves and drag/resize proposals; explicit review/apply |
| Saved plans/structure | Persistent multi-project scope, custom portfolio levels linked to a combined work tree, deduplicated progress, saved views and revision checks |
| Program board | Teams, hours/points capacity, iterations, drag/native allocation, warnings, conservative auto-allocation and named scenarios; dependency-safe dates within each iteration |
| Automation | Typed trigger/condition/branch/action editor, preview and execution audit; current owner permissions, per-rule savepoint rollback, recursion suppression and 1,000-action event budget |
| Forms/pages/reports/shortcuts | Typed visual intake, immutable answer snapshots on work-item detail/API and clones, revision-checked sanitized Markdown, actual creation/resolution/lead-time reports and safe links |
| Release tracks | Continuous/bundled explicit migration admission, monthly windows, immutable-image retry and deliberate recorded operator override |
| IP restrictions/insights | Install CIDRs with current-client/stale-write guards and trusted client identity; clearly defined rolling audited-actor counts |
| Sandboxes | Private synthetic-only PostgreSQL/uploads/secrets/web/worker; dedicated controller and fixed pool, TTL/delete, blocked outbound integrations and clean reuse |
| Cluster authorization | Owner-approved Node/RBAC on both control planes, scoped controller role verified at each endpoint, periodic fail-closed permission checks; temporary maintenance removed |
Twelve additive tables were introduced in migrations 20261018_0132 and 20261018_0133. Existing tenant/project rules, audit services and scheduling fingerprints remain authoritative. Plan commands require current revisions; application of dates is transactional and rejects stale work/dependencies. The final program regression applies sequential dependency dates within an iteration rather than assigning every work item the entire iteration span.
- 2143 passed, 199 skipped in the full final-source suite. Skips cover optional integrations/browser/PostgreSQL configurations; the relevant browser and PostgreSQL suites were separately enabled.
- 29 browser checks across existing/new journeys, desktop/phone and light/dark. The seven new workspace screens plus four administration screens received 36 layout/accessibility checks; intake and date-edit flows were also exercised.
- 22 PostgreSQL checks including additive migration round trips and stale/concurrent planning commands; 60 final focused checks cover the last constraints, audit, performance and localization changes.
- Fresh backup
serviceops-premium-rbac-backup-20261018restored successfully inserviceops-premium-rbac-restore-20261018before the final Helm upgrade. - 91 changed runtime hashes match the deployed immutable candidate. Health/readiness, web/workers/controller, retained Helm test and recent new-pod logs passed. Public API OpenAPI returns 200; the website retains the intended Cloudflare Access redirect.
- Production remains 487 tickets, 1068 users, 4 projects and 50 work items. Database/uploads/backup PVC identities are unchanged. Schema has 181 tables.
- Live sandbox: 0 tickets, 1 user, 2 synthetic projects, 14 work items; production PostgreSQL/Internet connections denied, DNS allowed. Real program allocation/review/apply changed 14 synthetic work items with zero dependency conflicts. Production Secret/deployment/PV access denied; only the intended sandbox/pool permissions allowed.
- Both temporary live environments were deleted. Reusing the same slot removed the previous database marker and nested upload. Both control-plane endpoints and 32 configured workloads passed the RBAC verification; scaled-to-zero workloads remain intentionally stopped.
Machine-readable acceptance · Sandbox lifecycle · RBAC matrix.
Production browser sign-in was not exercised. Normal-login browser QA used isolated SQLite; deployed PostgreSQL/domain, network and sandbox checks are separate evidence. No GitHub publishing or version bump was performed.
These are synthetic browser-QA screens, not a signed-in production session.
Usage and bounded contracts · Capability inventory and remaining Jira/JSM work. Team/iteration capacity is not a leave calendar or optimal solver. Scenario restoration changes plan proposals; dates require explicit review/apply. Reports do not provide a control chart. Multi-project release visibility is not a new shared release lifecycle. Automation lacks scheduled/external actions and retries. Storage capacity, financially backed uptime and staffed support are operator/service commitments. The screenshots also include third-party portfolio functionality; no blanket vendor-product parity is claimed.
Primary references: Jira Premium, Program board, Release tracks, Kubernetes network policies, RBAC.