Governance — Jira · Confluence · Compass
The same shape the code follows (CORE/MODULES/APPS) is mirrored in the delivery systems. When you add or rename something, update it in each: Git holds the code, Jira the delivery backlog, Compass the system-of-record catalog, Confluence the handbook.
Jira Cloud, company-managed, Standard tier, clustersco.atlassian.net. One shared set of
schemes across every software project — per-project difference lives only on boards, never by
forking schemes.
Taxonomy (mirror of the architecture)
| Concept | Jira | Compass |
|---|---|---|
| Product line | Project Category (ClusterCore; future Restrodesk) | — |
| Core / Platform | Platform project per core (CCORE) | base service |
| Product / App | App project per product (BGV, CLUS) | assembled app |
| Module | Component (mirrors the Compass name) + Lead | one service entry |
| Client / Account | a field (Client/Account) + per-client Versions — never a project-per-client | — |
Customer support is the JSM project Clustersco Support, never a software project. Compass is the source of truth for services/ownership/dependencies; Jira Components mirror Compass names.
The gated workflow
Three workflows by issue type — Delivery (Story/Task), Bug, Simple (Epic/Spike/Sub-task). The gates that matter:
- DoR (→ Ready for Dev): Acceptance Criteria + estimate required.
- Code Review (→ In QA): ≥1 approval + CI green + merged (Bitbucket-enforced — matches the git workflow merge gates).
- DoD (→ Done): Fix Version + Resolution set (Bugs also need Root Cause).
- Blocking is a flag, not a status — flagged items surface as a swimlane and keep their real status.
- Access via groups, never individuals (
clustersco-admins/maintainers/developers/qa/…); 2FA enforced. - Versions match SemVer /
version.yml; Fix Version powers the DoD gate and Release Burndown.
Boards
- One Scrum board per project (every App + Platform project): 2-week sprints, Story-point
(Fibonacci) estimation, Blocked =
flagged is not EMPTYswimlane. - One category-based Kanban ops board per line, built from a saved filter (not "from a project").
- Modules / clients / epics are filters / swimlanes, never new boards.
Confluence
The engineering handbook lives in the ENG space: Ways of Working, Engineering Standards (Git Workflow, DoR, DoD), Jira & Project Management, ADRs, Security & Access, Service Management. This docs site is the living companion to it.