Skip to content

docs(parity): planninq capability matrix, 157 rows against five competitors - #645

Merged
rubenvdlinde merged 7 commits into
developmentfrom
feat/parity-capability-matrix
Sep 26, 2026
Merged

rubenvdlinde merged 7 commits into
developmentfrom
feat/parity-capability-matrix

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

What this is

planninq's capability matrix at openspec/parity/capabilities.json, the same treatment nine products have had this week. It is a data file only: no page is wired to it and no code changes. A JSON file under openspec/ cannot affect the product's suites, so they were not run.

The code read is planninq development at 096d03b.

Category

Team project and task management inside Nextcloud. That covers:

  • projects with members
  • a kanban board per project with work in progress limits
  • a backlog
  • a task page with comments, attachments and dependencies
  • a per-project Gantt timeline
  • due reminders
  • personal time logging with a timesheet
  • a capacity and portfolio view

It is for internal IT, development and project teams in Dutch public organisations. It is not rostering or shift planning, which humaniq owns, and not booking of rooms or equipment. The category was decided from the code and from the product's own description, which positions it between Deck and Jira.

Columns and why

system grade read on yes partial no unknown
planninq (self) code reading 2026-09-26 39 30 87 1
Nextcloud Deck 1.18 driven 2026-09-13 60 25 72 0
OpenProject 16 Community driven 2026-09-12 101 32 24 0
Plane Community 1.4 driven 2026-09-12 61 31 64 1
Kanboard 1.2 driven 2026-09-13 70 40 47 0
Jira Software Data Center 11 docs-only 2026-09-13 89 35 30 3

Counts are over all 157 rows, including the 9 pending ones.

Why these five:

  • Deck is on the same platform and free, so it is the first thing a Nextcloud buyer compares against.
  • OpenProject, Plane and Kanboard are the open source project management suites a public buyer can self-host.
  • Jira is the market leader, and the product's own description names it as the complexity planninq avoids.

The round-4 corpus drove the first four. Every cell cites the round-4 file where one settles it. Jira is closed source and rated from Atlassian documentation only.

Left out:

  • Taiga, Huly, Redmine and Easy Redmine: they also have round-4 drives under procest/. They stay out to keep the matrix at five columns, and because each overlaps a chosen column: Taiga's agile boards and sprints are Plane's ground, and Redmine and Easy Redmine are the issue-tracker lineage OpenProject descends from. Adding any of them is a cheap follow-up, since the drive exists.
  • GitLab and Gitea (also driven): developer-forge issue boards rather than team project management.
  • Wekan, Focalboard and Leantime: not driven at all.
  • Microsoft Planner and Asana: SaaS-only, which rules them out for this buyer.

Two trees under two columns

Deck. Cells whose evidence starts with source were read from the tagged source at v1.18.4, not driven. The column stays graded driven, because the round-4 drive stands. In four places the source contradicts round-4:

  • Deck ships a Gantt view with drag to reschedule, so pln-gantt is yes.
  • Its view modes are kanban and gantt, not board and list.
  • BoardExportModal exports CSV.
  • ACardEvent implements IWebhookCompatibleEvent.

Kanboard's source cells were read at v1.2.54.

OpenProject. The drive ran on 16.6.10. The code reader read the 18.0-dev head 27a58131. Cells are rated for what a buyer can install today, the released 17.x line up to v17.8.0:

  • Every yes or partial cell citing the dev head had its paths checked against the v17.8.0 tag through the GitHub contents API. All but one resolve there: include_spent_time.rb exists only on the dev head, and the docs cited for that cell exist at v17.8.0.
  • Features shipped after the drive say so in the evidence: the Jira migrator in 17.2 and the schedule and availability page.
  • Backlog work package filters ship in 17.9.0, which has a release date of 2026-09-30 and was not out on 2026-09-26. So bkl-sort-filter is partial: at v17.8.0 only bucket and sprint containers can be filtered.
  • The mobile app is a beta, so partial.

The column stays driven, because the M1 column and the code census came from the drive.

Plane was read at the exact round-4 commit 2f895b82 (1.4.2). Absences that exist only on Pro, Business or cloud plans are rated no, with the plan named.

Rows and split

157 rows in 10 areas:

  • projects
  • boards
  • tasks
  • backlog
  • planning
  • time
  • portfolio
  • collaboration
  • integration
  • platform

148 rows are rated and 9 are pending (schema declarations with no form or screen): prj-phases, tsk-types, tsk-custom-fields, tsk-watchers, bkl-story-points, bkl-epics, tim-billable, tim-rates, col-notification-settings.

85 rows come from our own code and 72 from what competitors do. The competitor-derived rows are where the gaps sit: 34 rows have planninq at no while at least three competitors are at yes.

Ten sample rows

Cells are in the order planninq, deck, openproject, plane, kanboard, jira.

id row cells
brd-kanban Work a project's tasks on a kanban board. yes yes yes yes yes yes
brd-wip-limits Set a work in progress limit per column and see when a column goes over it. no no no no yes yes
brd-quick-add Add a card straight into a column from the board. no yes yes yes yes partial
pln-gantt See a project's tasks on a Gantt timeline. yes yes yes yes no yes
pln-dependencies Mark a task as blocked by another task. no yes yes yes yes yes
pln-due-reminder Get a reminder before a task falls due. yes partial partial no partial partial
tim-timesheet See your own logged time as a timesheet grouped by date. yes no yes no partial no
bkl-sprints Plan work in sprints with a start and end date. no no yes yes no yes
prj-contractor-portal Let an external contractor see the projects they work on in a portal. yes no no partial no no
prt-cycle-time See lead time and cycle time of finished tasks. no no no no yes yes

Claimed differentiators nobody has checked live

Each of these is a code reading where planninq is yes or partial and no competitor is yes. None has been driven.

  • prj-contractor-portal: the portaliq contribution provider
  • pln-due-reminder and pln-reminder-lead-time: the taskDueSoon rule plus the admin lead time
  • int-projects-widget and int-projects-on-client: the cross-app leaf; its "New project" button is broken, see defects
  • plt-nldesign
  • plt-audit-trail: provided by OpenRegister
  • col-live-updates
  • prt-project-capacity

The app's own appinfo/info.xml:10-20 is a second self-description. It claims WIP limits, a sortable and filterable backlog, configurable columns, filtering by assignee and priority, and dependencies with a blocked badge on the card. The code reading rates every one of those no: brd-wip-limits, bkl-sort-filter, brd-columns-edit, pln-dependencies and pln-blocked-badge. The product description over-claims the product.

Live-defect candidates

Every item here is a code reading that needs a live check.

Dependencies (the orphan components)

  • src/components/TaskDependencies.vue: a complete dependency editor (picker, blocked banner, remove buttons) that no view or component imports.
    • It is the only caller of src/store/dependencies.js createEdge and deleteEdge.
    • So lib/Service/DependencyService.php:112-236 (self, duplicate, cross-project and cycle validation) is unreachable.
  • src/components/BlockedBadge.vue: never imported. src/utils/taskHelpers.js:105 isBlocked() and :135 blockedTaskIds() are never called outside their own file.
  • src/store/dependencies.js:81: createEdge() takes no type, so the relates and duplicates edges the schema declares can never be created.

Board, columns and tasks

  • src/views/ProjectBoard.vue:283-291: columns() ignores the column schema and maps hardcoded BOARD_STATUSES. The column objects that src/store/projects.js:469 writes at project creation, including wipLimit, are never rendered.
  • src/store/projects.js:96-111: getDefaultColumns() reads loadState('planninq','default_columns'), but nothing in lib/ calls provideInitialState. The admin's column titles in src/views/settings/Settings.vue:430-495 never reach the frontend.
  • task.columnOrder is declared and never read or written in src/.
  • No task-creation UI or store action exists anywhere in src/: brd-quick-add, and tsk-create-edit is only partial.
  • src/views/ProjectBacklog.vue:20-26 is a placeholder page, so every backlog row is no.
  • src/dialogs/ProjectCreationDialog.vue:113-118: no field for the schema's key.
  • src/components/ProjectSettingsSidebar.vue: no unarchive action. At :16-64 there are no fields for billable, budgetHours, budgetAmount or hourlyRate.
  • src/utils/taskHelpers.js:34 hides the library's CnTagsTab and CnTasksTab with no substitute. As a result, labels cannot be attached to a task and task.parent subtasks are unreachable.
  • src/views/TaskDetail.vue:129-137 does not bind @mention on CnObjectSidebar, so the library's mention notification is dead.

Time

  • src/dialogs/TimeEntryDialog.vue has no billable toggle and no hourly rate. plannedTimeEntry.billable and hourlyRate can never be set.
  • The TimeSpentReport in src/manifest.json has no per-project grouping.

Portfolio and reports

  • src/manifest.json:151,163: the Capacity page note and card promise one row per assignee, but src/views/Portfolio.vue:139-147 builds one row per project.
  • src/manifest.json:97-110: the "Projects I am in" KPI has no member filter, so an admin counts every project.
  • src/manifest.json:162: the Task status card promises overdue, but nothing in :176-181 computes it.

Integration

  • src/integrations/CnProjectsWidget.vue:377-384: "New project" opens /projects?new=1&client=<uuid>, which src/views/ProjectList.vue never reads.

Members and access

  • src/components/MemberSearch.vue:124 calls /ocs/v2.php/cloud/users, which returns empty for users who are neither admin nor subadmin. A non-admin owner therefore finds nobody to add.
  • The same line builds the URL with generateUrl instead of generateOcsUrl.
  • lib/Settings/planninq_register.json:1118: dependency read is granted to every authenticated user, so a non-member can list any project's edges. Low impact.

Demo data

  • lib/Settings/planninq_mock_register.json:135,155,175: demo projects have members: [], so src/store/projects.js:195 hides them from everyone.
  • :123-140 holds placeholder values that reference nil uuids.
  • :69-70 has dependency edges pointing a task at itself.
  • The main register ships sample data in components.objects on every install.

Translation

  • l10n/nl.json: 67 of 259 strings have no Dutch entry, found by script. The regex misses multi-line calls, so the true count may differ.

Outside the rows

  • appinfo/info.xml:13 claims filters the board lacks.
  • The board gets no live updates.
  • The keyboard-navigation change proposal is stale.

Backends no page reaches

  • GET /api/projects/check-create-policy: has no frontend caller. It is only called internally, from ProjectController::create (lib/Controller/ProjectController.php:229).
  • POST /api/dependencies and DELETE /api/dependencies/{id}: called only from the orphan TaskDependencies.vue.
  • projectPhase schema: declared, with no screen.
  • column schema: written, never read.
  • plannedTimeEntry.billable and hourlyRate: declared, with no form field.
  • project.budgetHours, budgetAmount and hourlyRate: declared, with no form field.
  • task.storyPoints, epic, watchers, issueType, metadata, parent, completedAt and resolvedAt: declared, never read or written in src/.

Where the method was harder than the skill says

The research sat under another product's slug. The competitor drives for this category are filed under procest/ in the market-intelligence corpus: nextcloud-deck, openproject, plane, kanboard and jira-data-center under procest/<system>/round4/. procest is dossiq's old slug, for case management, and it names no planninq or planix product. The corpus was written for a case-management row set, so many of our rows are not covered directly. The menu trees, code censuses and journeys still settled a lot. The research repo mentions planix or planninq only in the portfolio spec and in procest round-2 compare notes.

Round-4 and the source disagree.

  • Deck: the four places listed above.
  • Plane: the source adds a "Make a copy" work-item action the corpus missed (no row changes), a hollow enableDependency prop on the Gantt, and an hours-estimate system flagged is_ee.

Two trees under OpenProject. The drive and the source read were two versions apart, and 17.9 was announced but not released. Rating what can be installed today took a tag-by-tag path check.

The self-description over-credits. info.xml, the manifest page notes and the column schema all describe a board with WIP limits and a backlog. The components render hardcoded lanes and a placeholder. Reading declarations would have credited about ten rows that do not work.

Readers died on the throttle.

  • The first lane and its readers were stopped by an account session limit.
  • On relaunch, three Sonnet readers died within minutes on the server-side throttle ("not your usage limit") before writing a pack.
  • Every reader after that ran on Opus. All seven packs landed complete.

Verify

python3 _lane/hydra/parity_verify.py --strict openspec/parity/capabilities.json

parity-verify: openspec/parity/capabilities.json
  148 rated rows, 9 pending, 6 systems

unknown-cells  (1)
    5 cells rate unknown. That is legitimate, and it is listed so it cannot hide: capabilities[brd-keyboard-move] jira, capabilities[prt-leave-aware] jira, capabilities[prt-placeholder] jira, capabilities[int-mobile] plane, capabilities[plt-accessibility] planninq

1 finding(s) in 1 check(s)

Only the unknown census remains. The strict run exits 1 on that listing alone.

🤖 Generated with Claude Code

@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/planninq @ f11f795

Check PHP Vue Security License Tests
lint ✅
phpcs ✅
phpmd ✅
psalm ✅
phpstan ✅
phpmetrics ✅
eslint ✅
stylelint ✅
build ✅
check-manifest ✅
check-l10n-js ✅
check-schema-l10n ✅
composer ✅ ✅ 107/107
npm ✅ ✅ 646/646
app:check-code ⏭️
info.xml ✅
REUSE ❌
lockfile sync ✅
PHPUnit ⏭️ not run for this diff — no file in this diff matches the code globs, and none carries a source extension — the heavy tier has nothing to decide about it.
Newman ✅
Playwright ⏭️ deferred: E2E runs locally and on the promotion path only. This pull request targets development, so the suite is asked once per promotion into beta and main rather than once per push per open pull request. Run it on any branch from the Actions tab, or locally with npx playwright test.
Hydra gates ✅

Quality workflow — 2026-09-26 11:48 UTC

Download the full PDF report from the workflow artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant