v10.22 2026-07-22 WeKan ® release

This release adds the following features:

• Admin Panel / Problems “Status” overview + snap run wekan.problems. Problems / Summary now shows everything in progress (database text migration, board data-repair, recovery, cron migration, attachment migration), detected problems (broken cards), and a login-page checklist of the causes that make the login page show “Must be logged in” or sit on the logo + “Loading, please wait.” spinner (a migration/repair running, wrong/unset ROOT_URL, LDAP, Sandstorm). The same overview is available WITHOUT the Admin Panel from the server command line — snap run wekan.problems (with migrations / login / broken-cards / cpu sub-commands) — so an admin with only server access can read it. Migration/repair progress is persisted to the database so a separate process can see it. Docs: docs/Features/Admin-Panel/Problems/ . Thanks to xet7.

• Shared board data-repairs run on board open, on server startup, AND during the MongoDB <-> FerretDB v1 (SQLite) text migration — shown in one blue, Product-name-branded progress dashboard. Beyond the #6484 list-unbind, the shared set now also fixes cards with no swimlane and orphaned cards whose swimlane was deleted (invisible cards), reassigning them to the board’s first swimlane. The repairs run SERVER-SIDE and do not depend on a user watching a progress page: a version-gated background pass runs once at startup, board open repairs per board, and the database migration repairs the live data before copying so the migrated copy is clean too. The progress dashboard is mounted app-wide (board + Admin Panel), styled in WeKan blue (#2980b9), and branded with the configured Product name . Thanks to xet7.

This release fixes the following bugs:

• FerretDB high CPU: run FerretDB standalone (no OpLog) by default. Several sites reported the ferretdb process pegging ~2 CPU cores for a long time while the WeKan node process sat idle — pages taking 5+ minutes, All Boards counts stuck at 0, raw i18n keys, and the login page showing “Must be logged in” or a stuck “Loading, please wait.” spinner. That idle-node / pegged-ferretdb split is the signature of an OpLog tail: Meteor holds a tailable cursor on local.oplog.rs and FerretDB re-scans it server-side. wekan-control already defaulted to polling-only, but ferretdb-control passed --repl-set-name unconditionally, so FerretDB always maintained the capped OpLog even when WeKan would not tail it. It now runs STANDALONE in the default polling mode and enables the replica set / OpLog only when wekan-ferretdb-oplog=true. Opting into OpLog is also cheaper now on the FerretDB v1 fork side (the {ts: {$gt}} tail filter is pushed down to SQL and the OpLog Timestamp is indexed). See docs/Features/Admin-Panel/Problems/Migrations.md . Thanks to xet7.

• Fix #6504: a rule that moves a card to another board failed with “newBoard.getNextCardNumber is not a function”. On the server ReactiveCache.getBoard() is async; the cross-board branch of Cards.move() used it without await, so the destination board was a Promise (its methods missing) and label carry-over from the source board was silently dropped. Both getBoard() calls are now awaited (same fix as PR #6505). Thanks to ChristianMa97 and xet7.

• Swimlanes view: a shared card no longer appears in every swimlane (“doubled cards”). A card with no swimlane (swimlaneId null / ” — a shared / pre-migration card) was surfaced in EVERY swimlane, so on a board with several swimlanes the same card rendered once per swimlane (and the extra DOM contributed to the search hang / can’t-scroll on big boards). A non-first swimlane now shows only its own cards; shared and orphaned cards surface ONCE, in the first swimlane, so a card is never shown in more than one swimlane. Board-wide label filtering (#6441) is preserved. Thanks to xet7.

• Repair for boards where a list “disappeared” from swimlanes (the #6484 corruption). The #6484 bug — nudging a board-wide list in swimlanes view bound it to one swimlane and moved its cards there, so it vanished from the other swimlanes — was fixed in code, but boards already hit keep the wrongly-set list.swimlaneId. A new board-admin method repairBoardWideLists(boardId) clears those lists back to board-wide (rendered under every swimlane); it is idempotent and scoped to the one board. (Cards the bug moved into one swimlane are not restored — recover those from a backup.) . Thanks to xet7.

• Opening a board now auto-detects the #6484 corruption and repairs it. On board open, a cheap boardListRepairNeeded check reports whether any list is wrongly bound to a swimlane; if so and the viewer is a board admin, repairBoardWideLists runs automatically while a progress modal is shown, then completes. The check runs once per board, fire-and-forget, and never blocks rendering. The migration-progress modal is now branded with the configured Product name (Admin Panel / Settings / Layout / Product name), falling back to WeKan when none is set, so every migration reusing the modal shows the admin’s Product name instead of the hard-coded brand . Thanks to xet7.

Thanks to above GitHub users for their contributions and translators for their translations.