Sample Projects Walkthrough

Learn project management with realistic sample projects

The current project interface uses the Jira-inspired workspace design, deployed on Helm 219. The screenshots further below preserve the original review state.

Three private demo projects were created in the live MicroK8s application on 17 October 2026. All work is labelled demo/learning and remains unassigned. No actual infrastructure changes, compliance results or historical delivery performance are claimed.

Project	Practice scenario
DEMOCLOUD	Cloud foundation, database migration, recovery and release readiness
DEMOPORT	Customer journey, sign-in, request submission, accessibility and handover
DEMOAUDIT	Audit evidence, access review, remediation, tabletop and readiness decision

Each has 16 work items, including two epics and six subtasks; three components; two demo release versions; and completed, active and planned sprints. Across the projects there are 48 work items and nine sprints. The earlier LEARN project and its two tasks remain available.

Try this walkthrough

Open the cloud Board and move a card between columns. Reload to see the saved state. On a phone, swipe the board horizontally; the task Details status selector is the alternative to dragging.
Open DEMOCLOUD-5, then its subtasks. The chain reaches DEMOCLOUD-14, with four nested subtask levels below the story. Follow the breadcrumbs to navigate back.
Open DEMOCLOUD-6. Review its blocker and parallel subtasks. Add a comment or a practice work log, then inspect Activity and the remaining estimate.
Use Backlog and sprints to move a backlog task into the planned sprint. Subtasks follow their parent and are not counted as separate sprint commitments.
Open the active sprint report, then browse the completed sprint. Counts, points and time estimates are different units. The completed example was simulated on creation day; its chart is not evidence of weeks of past delivery.
Use Cross-project planning to inspect the cloud-to-portal blocker and intentional date conflicts. A date shift is an unsaved preview, not a stored reschedule.
Search work items with project = DEMOCLOUD AND sprint IN openSprints(). Explore Components and Releases to see another way of organising the same work.

Review evidence and limits

Live readback confirmed three private projects, 48 work items, nine sprint states and no assignees. Creation used the application service layer, including permission checks and audit/history creation, rather than direct SQL inserts. Data creation required no application release or deployment.

Browser QA used the identical scenario definitions with a disposable SQLite database, normal password login and CSRF protection. The 44 changed runtime file hashes in the existing QA source matched the deployed candidate source manifest. The running image was independently confirmed as sha256:27130bd77a8fbf7e18347687c48ccb59cd0702c1792c91ae0c3aa0afacaabe9b.

30 page/layout checks: 15 pages at 1440 px and 390 px. All returned HTTP 200; no WCAG A/AA violations were reported by axe; no document-wide horizontal overflow was detected.
Six desktop interaction checks passed: pointer drag with reload persistence; comment save; work-log save; backlog-to-sprint move; schedule-preview notice; complete ancestor breadcrumbs.
No JavaScript page errors or failed HTTP responses occurred during the successful review run.
A first automated drag attempt used unstable coordinates after scrolling and did not target the expected card. A diagnostic rerun used stable visible coordinates, recorded drag events for the correct card and verified persistence after reload. This was a test-harness correction, not an application fix.
Phone layouts were inspected visually; touch drag and mobile mutation flows were not exercised. Dark themes, screen-reader operation, production-scale load, production database concurrency and the public Access login flow were not retested in this review.
Automatic approval review rejected a proposed live browser session created outside normal authentication. That method was not executed. No production secret or browser credential was extracted. Live data verification and isolated UI evidence are separate.

Detailed results: review.json.

Original UI findings — resolved on Helm 218

Priority	Finding	Impact
P2	A flagged task has no flag indicator on its board card.	DEMOCLOUD-6 is flagged, but its blocker status is easy to miss on the board.
P3	Search help says sprint queries are unsupported even though sprint filtering works.	Misleading guidance makes the working search feature harder to discover.
P3	Sprint action links wrap awkwardly on a narrow phone layout.	Report/board actions need a clearer stacked or wrapping action layout.

All three findings were subsequently fixed and deployed on Helm 218. See fixes and verification for current screenshots and evidence. The screenshots below retain the original review state.