Skip to content

Project Workspace Design

Anushka Wijesundara edited this page Oct 18, 2026 · 2 revisions

Jira-inspired project workspace

Delivered on local MicroK8s Helm 219, 17 October 2026. Open the cloud demo board to try it.

Area Interface change
Navigation A light project sidebar keeps Overview, Backlog, Board, List, Sprints and reports, Releases and Components together. Project settings remain restricted to project administrators. All projects returns to the project directory.
Board Compact project heading, familiar view tabs, slim search/filter controls, flat cards, neutral columns, type/priority/estimate metadata and visible flags. Quick creation and drag-and-drop remain available.
Backlog A sprint navigation pane shows active/planned sprints beside the work list on desktop. The selected sprint has clear actions and status. The layout stacks on phones; ranking, bulk assignment, history and reports keep their existing behaviour.
Work item A focused title/action row, clean content sections, ancestor breadcrumbs and a right-hand details pane replace heavy nested panels. Forms, comments, attachments and time tracking retain their existing contracts.
Themes and mobile The layout supports light/dark themes, keyboard focus and phone widths. On phones, the board scrolls within its own container; the document does not become wider than the viewport.

The visual direction follows familiar Jira board/backlog organisation and project navigation. ServiceOps branding and existing permission/data models are retained. This is a project-management interface redesign, not a claim of full Jira feature parity or a change to the ITSM ticket module.

Validation and delivery

  • 18 Chromium workflow cases passed, covering board interactions, project pages, nested work, sprint lifecycle, search, flags, link destinations, desktop heading clearance and contextual navigation. Light/dark and desktop/phone layouts are included.
  • 112 focused tests passed; two optional tests skipped, including explicit admin/member/viewer navigation checks. Private-project names stay hidden from unauthorised users and settings remain protected server-side.
  • 30 realistic page/layout checks passed using the three complex demo scenarios at 1440 px and 390 px: no axe WCAG A/AA violations, document-wide overflow, JavaScript page errors or failed HTTP responses. Phone mutation workflows and touch dragging were not separately exercised.
  • Screenshot review caught fixed-header clearance and inherited sidebar contrast problems during development. Both were corrected before the final passing runs. The final regression checks prevent the heading from disappearing under the top bar.
  • Ruff, whitespace, locale extraction consistency, generated dark CSS and Helm lint passed. No migration or backend workflow change was introduced.
  • A fresh PostgreSQL backup restored 165 tables, 487 tickets, four projects and 50 work items, at head 20261017_0130, into an isolated scratch database which was then dropped.
  • Helm 219, web/outbox/events/AI readiness, health/readiness, retained Helm test, 45 runtime source hashes, PVC identities and recent error logs were verified. Public API returns 200 and the website remains behind Cloudflare Access.
  • Browser QA used disposable SQLite data with normal password login and CSRF enabled. Public authenticated sign-in, a production browser session, PostgreSQL concurrency and production-scale load were not retested. No production credential extraction or authentication bypass was used.
  • Version remains 1.113.50. No GitHub commit, push, tag or pipeline was requested or performed. The remaining Premium programme stays open.

Live acceptance · Source manifest · Browser results · Functional results · Realistic UI review · Backup · Helm health test

Screenshots

These show isolated normal-login QA with the deployed source and realistic demo data.

Project board and contextual navigation

Sprint navigation beside the backlog

Focused work item and right-hand details

Dark project workspace

Phone board

Clone this wiki locally