A list can be split into Doing and Done (models/lib/boardFlowPolicies.js):
a card of it marked Done here, with the circle at its minicard's corner,
waits dimmed and edged green to be pulled into the next list, and the
list header counts Doing and Done. The mark names the list it was made in
(card.flow.splitDoneListId, written by setCardFlow from the card's own
list, and only in a split list), so a card moved on is in Doing of its new
list without anybody clearing it.
A board admin allows split lists in Board Settings / List, and each list
is split from its menu. Admin Panel / Settings / Visibility / Features /
Split lists hides it on every board. Translated in every language.
Thanks to xet7 !
Two Scrum meeting helpers, offline and with no AI
(models/lib/scrumMeetings.js, docs/Features/Scrum/Meetings.md):
- Daily standup: the board's active members in a shuffled order, each
with the same timebox (Minutes per person in the Scrum settings, 1-15,
2 by default), counted down and red once over; Next hands over, and the
end says how long it took. It runs in the browser and writes nothing.
- Retrospective board: a new private board, titled with this board's name
and the day, with the lists Start doing, Stop doing, Keep doing and
Action items, made through createBoardWithInitialSwimlanes so "who may
create boards" applies.
Both are in the board menu for every member, next to Summary. Each is
turned off for one board in its Scrum settings and for the instance in
Admin Panel / Settings / Visibility / Features. Translated in every
language.
Thanks to xet7 !
Kanban practices for a board's lists (models/lib/boardFlowPolicies.js,
docs/Features/Lists/Flow-Policies.md), offline and with no AI:
- List policy: each list's own entry and exit criteria, written from the
list menu and shown as a gavel at the list header, its tooltip the text.
- Commitment point: the list from which work is committed to, flagged at
its header; the lists before it are options.
- WIP limit per person: how many open cards one person may hold on the
board; an opened card names each of its people over it.
Each is off until a board admin turns it on in Board Settings / List, and
each is a feature of Admin Panel / Settings / Visibility / Features, which
hides it on every board.
The Scrum settings get a Definition of Ready beside the Definition of
Done, and both are now readable by every member in the Scrum views once
written. The four Scrum translation guards count 128 keys with it.
Translated in every language.
Thanks to xet7 !
Four Kanban and Scrum practices other tools have, kept on the card
(card.flow, models/lib/cardFlow.js), offline and with no AI:
- Blocked: ticked with a reason; who marked it and since when are the
server's. A red Blocked badge on the minicard, the reason its tooltip.
- Class of service: Standard, Fixed date, Expedite, Intangible. Expedite
has a WIP limit of one open card per board; a second is refused.
- MoSCoW priority: Must, Should, Could, Won't have.
- WSJF score: business value, time criticality and risk reduction divided
by job size, each on the 1-20 scale; shown once every part is set.
Each is a row of Board Settings / Card in the Card section, off on the
card and the minicard until a board turns it on, and an Admin Panel /
Features / Card field that hides it on every board. Written only by the
setCardFlow method, which checks the card edit right, an assigned-only
member's own cards and the values; a client write of flow is denied.
Translated in every language.
Thanks to xet7 !
They were the last files the Import page read itself and sent whole. A
chosen Jira file is now uploaded like the other sources: the people of
its map-members step are read from it by the server (the Jira mapper is
shared, models/lib/jiraMembersMapper.js), and the estimate mapping goes
with the import call. A CSV / TSV file's header, sample rows and guessed
mapping come from the server (csvUploadPreview), its people from the
columns chosen (csvUploadPeople), and the import parses it there. Both
methods read only the sender's own upload, signed in and while import is
enabled, and leave it for the import that follows.
Thanks to xet7 !
Added after comparing WeKan's charts with the reports of Jira, Azure
DevOps, Nave, ActionableAgile and the Flow Framework: Created vs.
Resolved, Net Flow, Time in List, Average Age, Throughput Run Chart and
Due Date Performance under Kanban flow; Release Burndown and Epic
Progress under Scrum; Workload, Distribution, Dependency Map and Activity
Heatmap under Overview. Each opens like the other charts, with the export
bar at its top, a Chart.js chart and its data table, which is also what
its PDF and Excel export write.
The calculations are pure (models/lib/boardReports.js) and answer one
shape, { bars, table }, so the chart view and both exports read every
report the same way; the server loads only what a report reads. A member
who may see only their assigned cards gets none of them, as with the
other charts. The report names and table headings are translated into
every language.
Thanks to xet7 !
A file chosen on the Import page for the generalized importer's sources
is POSTed to /api/import/upload/:source and written to
WRITABLE_PATH/import-uploads a part at a time, instead of being read in
the browser and sent whole, as text or base64, through importBoard. The
size the browser announces is checked before the first byte against the
largest import set in Admin Panel / Settings / Security (none: no limit)
and against the free space of that disk less a reserve, and the space is
checked again every 64 MB while it is written; a refused or interrupted
upload leaves no file behind. importBoard then reads the file by its
id: a .zip export (Slack, Google Takeout, Vikunja, Notion, Plane) is
opened from the disk, its entries inflating up to the limit or the free
space, and a mailbox is read a message at a time, also inside a Takeout
zip. The upload is removed once read, or after an hour.
The HTML-only mail text is read through the parsed document rather than
stripped with a pattern. TODO.md says what is left of large files, and
which locale files hold another language.
Thanks to xet7 !
The Board View menu, and Board Settings / Board View, show the views in six
groups - Board, Calendar and time, Scrum, Kanban flow, Overview, and
Communication and code - with the board's own order inside each; the six
separators of the old order are the headings now. The Import page and the
Export menu list the other tools under the same headings from one table,
models/lib/toolGroups.js: Kanban and project tools, Issue trackers and
version control, Task and to-do apps, Spreadsheets and tables, Text and
outlines, Mail, calendars, chats and notes, and Fetched from a service.
The thirteen headings are translated into every language; "Scrum" stays
as it is, like the other method names. The Tigre instructions of the new
imports keep the attested plural for files.
Thanks to xet7 !
The Import page reads nine more kinds of export, each into the view it
is for: mail (mbox, .eml) as cards of Board View / Email, one per
conversation with the replies as comments; an .ics file's tasks by
status and its events, with their dates; a Google Takeout .zip as one
board with a swimlane per product (Mail, Tasks, Keep, Calendar, Google
Chat); a Slack workspace export, a Mattermost bulk export, Telegram
Desktop's JSON, a WhatsApp chat .txt and a DiscordChatExporter JSON as
channels whose messages are comments, for Board View / Chat; and an
Evernote .enex as notes with their to-dos as checklists. The Export menu
writes a board as an .mbox, an .enex and a Mattermost bulk import file,
each read back by the same import.
MIME is decoded with mailparser and ENEX with htmlparser2 on the server,
and the zips are read under the zip-bomb guards of the other zip imports.
An imported message's Message-IDs pass the import sanitizer without
their brackets, so a later reply to the board joins the thread. The
instructions of the nine are translated into every language. TODO.md
also gets the next items: grouped menus, large-file import and export,
and the reports to add.
Thanks to xet7 !
Which group kinds - Organizations, Teams, email Domains - Admin Panel /
People / Shared templates allows came from the browser's localStorage,
so it differed per browser and was empty for every user but the admin
who ticked it. It is Settings.sharedTemplatesScopes now, published to
every client, and an admin's earlier ticks are carried over once.
The All Boards / Templates targets were empty for everyone anyway:
getMyShareableGroups did not await ReactiveCache.getUser, so it read
orgs, teams and emails from a Promise.
Thanks to xet7 !
The entry was commented out for the #4214 "icons random dance", which
left the popup - card counters and member avatars on All Boards, card
aging, auto-archive and personal list widths - with no way in. The All
Boards tiles now read one fetch of getAllBoardsTileData rather than
reactive cursors, so the loop cannot return.
Thanks to xet7 !
Runs one Playwright spec, found by its file name or a part of it, on the
browsers chosen, optionally only the tests whose title matches. Also
./build.sh --playwright-spec <spec> [chromium|firefox|webkit|all] [filter].
A WeKan already answering on :3000 is used as it is. Otherwise a fresh
bundle is built and the test server started the way the whole-suite runs
start it (Meteor's mongod on :3001, the bundle on :3000), and both are
stopped afterwards, so a single spec does not pass or fail on a stale
bundle. In build.sh each browser runs natively when it can launch and in
the Playwright container when it cannot; Chromium in the VSCodium Flatpak
on arm64 runs natively without Docker. Logs go to
.tools/log/test-playwright-spec/<datetime>/.
Thanks to xet7 !
GET /api/boards/:boardId/lists/:listId/cards and
GET /api/boards/:boardId/swimlanes/:swimlaneId/cards now also return each
card's modifiedAt, dateLastActivity, labelIds, members and customFields
([{ _id, value }]), so a syncing client can skip unchanged cards instead
of a GET per card. Both routes build their items in
models/lib/restCardListItem.js, so they stay alike.
Same board access check, and no extra query. Admin-only custom field
values stay concealed by sendJsonResult's redaction, as on the single-card
GET; each item carries its boardId so that redaction is scoped to this
board, and an admin of it still reads a field shared with other boards.
Thanks to rmb82 and xet7 !
Fixes#6928,
The docs tree is laid out like the menus - a menu path is a docs path.
Admin Panel / Settings follows the new structure: Visibility.md is
Appearance.md, with new Features.md, Feature-Profiles.md, Security.md,
Activities-and-Notifications.md and Delete.md; the section indexes,
Admin-Panel.md, Admin-Panel-URLs.md (with the moved-pane redirects) and
Validation.md follow the live menus, and Who-Sees-What.md explains in one
place which layer decides what is shown and what is allowed.
Pages are added for the menu entries that had none, each written from
the code: every Admin Panel / Problems pane, the member menu, the board
header, Board Settings, the All Boards left menu, and the list,
swimlane and card menus. Older links to the moved panes are updated
across docs/.
TODO.md records what documenting the menus found: Edit Profile does not
save a username for non-admins, the Support page's signed-out case is
unreachable, Create board from this card is hidden from members who can
edit the card, All Boards Settings is unreachable, and the Share template
targets live in browser storage.
Thanks to xet7 !
Who sees and may use what was spread over three tabs: the feature
switches and feature profiles sat in Settings / Visibility beside the
logo and colours, and three settings (Security, Delete, Notifications)
sat in Problems among the reports, where they had landed when the
Features tab was removed.
- Settings / Visibility is Appearance (how this WeKan looks); its
Features and Feature profiles groups are panes of their own. One
template renders all three by `part`, so every field and Save is
unchanged.
- Problems / Security, Delete and Notifications are Settings /
Security, Delete and "Activities and notifications". Problems is
Summary, Backup and the Reports.
- Every old address redirects (MOVED_PANES / movedPanePath in
models/lib/adminUrls.js, applied by config/router.js).
- People, Teams and Organizations show the feature profile that
applies, so a profile can be found from either side.
- Two new labels, Appearance and Activities and notifications, are
translated into every language.
tests/adminPanelStructure.test.cjs and admin-panel-structure.e2e.js
cover the order, the redirects and that no feature switch is left in
Appearance or Problems; older guards and specs follow the new panes.
Thanks to xet7 !
A developer laptop with many programs open showed in Admin Panel /
Problems / Memory usage: "RamBleed, high, high RAM usage started
(>= 90%): RAM 16.1/30.9 GB (52%), swap 18.7/30.9 GB (60%)". Swap at or
above 25% started a high-memory period by itself, made it high severity,
and the text still said ">= 90%". Idle pages in swap while RAM is free
are not pressure.
- Swap now counts only while RAM is also at or above the low threshold
(80%), and a period ends when RAM is back under it.
- The start row says what started it: (RAM >= 90%) or (swap >= 25% with
RAM >= 80%). Only RAM at 95% or more is high severity.
- The RAM, CPU, disk and speed monitors named their rows like Hall of
Fame entries (RamBleed, CpuBleed, DiskBleed, SlowBleed) with CWE-400.
They are HighRamUsage, HighCpuUsage, HighDiskUsage and SlowRequest now,
without a CWE, and stored rows are renamed once at startup.
tests/ramHighTracker.test.cjs replays the laptop's numbers as a
negative case; tests/resourceStreamNames.test.cjs pins the names.
Thanks to xet7 !
Decided by the maintainer on 2026-11-18 (TODO.md): administrator-defined
profiles. Admin Panel / Settings / Visibility / Features gains Feature
profiles: a name, a tick for each optional feature the profile hides,
and the users, teams and organizations it applies to. A user's own
profile wins, then the first profile naming one of their teams, then one
naming one of their organizations.
Strictly opt-in, because hiding features by default was tried and
removed as a support nightmare: a user with no profile sees everything,
a profile only hides (no data or permission changes), and the member
menu tells the user which profile hides how many features. The decision
is models/lib/featureProfiles.js, applied in isFeatureAvailable, so
every existing place that hides a disabled feature follows it.
Profiles are stored in Settings (featureProfiles) and a direct
assignment on the user (featureProfileId, published to that user only
and not writable by them). tests/featureProfiles.test.cjs covers the
decision, cleaning, the admin-only methods and the wiring;
feature-profiles.e2e.js drives the page, the hidden board view and the
notice.
The 11 new strings are translated into every language. Low confidence:
qu, rup, rn, rw, sah, se, sm, sn, ss, st (low); sd, so, si, scn (medium); sr uses standard Тимови/Организације; ff, fj, gn, gv, haw (low); ha, hsb, fur, gd, ga, fo (medium); ace, ak, ay, bm, bi, bo, bua (low); ba, bho, ar-DZ/ar-EG/ary dialect spelling (medium); iu, kl, ks, kw, lld, lg, ig, la (low); kok (medium); tig, ti, tlh, ve-PP, ve-CC, uz-AR, ve, ts, tn, to, tpi (low); szl (medium); wal, vo, zgh, wa, wo, wa-RR, yi, wuu-Hans (low); chr, dz, ee, csb, cv, co, ckb (low); cmn uses 配置 for profile; nah, nap, nd, nso, om, mai (low); mg, ny, pap, or_IN, ps (medium).
Thanks to mimZD and xet7 !
Fixes#6837.
vscodium-sandbox.sh now grants --talk-name=org.freedesktop.Flatpak, so
build.sh's docker_exec can run Playwright Firefox and WebKit in the
official Playwright image when they cannot start inside the sandbox.
WEKAN_SANDBOX_HOST_DOCKER=0 leaves the grant out. The README says what it
costs: flatpak-spawn --host is a host escape and the Docker socket is
root-equivalent. The script gets a bash shebang, as it now uses an array.
Thanks to xet7 !
Board Settings / Swimlane / One shared list header row (#2805) only hid
the list headers of every swimlane but the first. Since lists belong to
a swimlane, the others kept lists of their own, so the one header row
did not match what was under it: a new swimlane showed no lists at all,
and each swimlane scrolled sideways on its own.
With the setting on, the Swimlanes view is now what swimlanes were
before lists belonged to one: every swimlane shows all of the board's
lists in their order, under the one header row, and the swimlanes
scroll sideways together (client/components/swimlanes/sharedListRow.js,
one capturing scroll listener that ignores the scroll events it causes,
so a shorter row cannot pull the others back). Each list still holds
the cards of the swimlane it is shown in. Nothing is written to a list
or a card, so on a board whose swimlanes have different lists, turning
the setting off shows each swimlane's own lists again. While it is on,
a list dropped under another swimlane is reordered, never moved there
with all its cards.
tests/sharedListRow6902.test.cjs drives the scrolling, including a row
that cannot scroll as far, and the Swimlanes view wiring, and
tests/playwright/specs/shared-list-row-6902.e2e.js checks the lists,
cards and scrolling of two swimlanes with the setting on and off.
Thanks to mimZD and xet7 !
Fixes#6902.
They act on the opened card, or on the hovered or selected minicard,
which is opened first, as the d due date shortcut does. Like d, they do
not open the popup themselves: client/lib/cardMenuHotkey.js clicks the
opened card's hamburger menu and then its Move Card or Copy Card item,
so the menu's permissions decide - Move Card for board admins, Copy
Card for everyone who is not a Worker. A menu without the item is
closed again. Shift keeps them apart from m (assign yourself) and c
(archive). The keyboard shortcuts list names them with the already
translated popup titles, and docs/Features/General/Keyboard-Shortcuts
lists the opened card's shortcuts.
findOpenedCardDetails() is shared from client/lib/dueDateHotkey.js.
tests/cardMenuKeyboardShortcut.test.cjs drives the DOM logic, including
a menu without the item, another opened card and a stray element, and
tests/playwright/specs/move-copy-keyboard-shortcut-6904.e2e.js presses
the keys, with shortcuts off, while typing, and as a non-admin member.
User-defined shortcuts, the question in the issue, are not part of this.
Thanks to mimZD and xet7 !
Fixes#6904.
The Dockerfile's METEOR_RELEASE is METEOR@3.6.1. The Bun build's
releases/bun/prepare-meteor.sh refused every release but 3.6; the 3.6
port (meteor-3.6.patch) applies unchanged to 3.6.1, checked with
git apply --check against 3.6.1's commit eaf13497, so 3.6.1 is accepted
pinned to that commit. The sandbox README names the current release.
Thanks to xet7 !
Dependabot alert #189: go.opentelemetry.io/otel/trace >= 1.35.0,
< 1.47.0 lets attribute values made of valid U+FFFD runes bypass
AttributeValueLengthLimit. govulncheck then also reported GO-2026-6865
in github.com/klauspost/compress 1.18.7, fixed in 1.20.2. Both are
indirect dependencies of docs/Databases/FerretDB/1/SpeedTest/embedded.
tests/goModuleFloors.test.cjs raises the floors for every go.mod in the
repository, with every OpenTelemetry module at 1.47.0, and rejects the
versions that were reported.
Thanks to dependabot and xet7 !
Admin Panel / People / Cloud and the Cloud Panel (73db2a28c3) are removed from
WeKan, with their methods, route, menu item, docs and tests. Many domains from
one Weddy is a Weddy feature: there every domain's WeKan is in one process,
where Node.js WeKan containers would have to work together, which gets
complicated. It is written in Go in caddy-wekan-plugin.
The translations of its strings stay: WeKan, Weddy and the rest use the same
WeKan translations.
Thanks to xet7 !
The Caddyfile example used `root /path`, which tests/caddyfileExamplesV2.test.cjs
rightly reads as Caddy v1. Weddy's wekan option is now `data`, and WeKan runs
inside Weddy in Go - no bundle, no WEDDY_TENANT - so the page says so, and that
the Cloud Panel's files are written by hand or by a Meteor WeKan until its Go
pages are done.
Thanks to xet7 !
Weddy (wekan/caddy-wekan-plugin) runs a WeKan for every domain, each in its own
directory - files/domains/<domain>/files/db/ for its database - and starts
the first domain's WeKan with WEDDY_CLOUD_DIR, every customer's with
WEDDY_TENANT=true.
- Admin Panel / People / Cloud, only in that first WeKan and only for a site
admin (a per-tenant admin's whitelisted menu never has it): Cloud Panel
Domain, e.g. cloud.wekan.team, and SuperAdmin Username, a username or
e-mail address.
- /cloud, the Cloud Panel, where the SuperAdmin is taken at the Cloud Panel
Domain: Settings with the left menus Domains and CloudFlare, in the Admin
Panel's layout. Domains is a table page - Domain, Customer name, Customer
email address, Billing email address, Start Date, End Date and the TLS
Weddy got - with a form to add and edit. CloudFlare is a write-only API
key field.
- server/methods/cloudPanel.js checks in every method again that the caller is
the SuperAdmin and the request's Host is the Cloud Panel Domain - not
X-Forwarded-Host, which a client could send itself. The collections are not
published. Every change writes WEDDY_CLOUD_DIR/domains.json for Weddy; the
key goes to cloudflare.json, mode 0600, and is never sent back.
- models/lib/cloudPanel.js has the rules, shared by client and server; its
domain rule is the same as Weddy's, since the name becomes a directory.
- Customers' WeKans show none of it.
The 15 new strings are added as pending Transifex, written in Finnish, and
translated into every other locale. Low-confidence translations: ace ak an ay
ba bho bi bm bo bua chr co csb cv dz ee ff fj fo fur gn gv haw hsb ht ig iu
kl kok ks kw lg lld mai mi nah nap nd nso oc om pap qu rm rn rup rw sah sc scn
se sm sn so ss st szl tig tlh tn to tpi ts uz-AR ve ve-CC ve-PP vo wa wa-RR
wal wo wuu-Hans yi zgh. Transifex translations replace them when they arrive.
tests/cloudPanel.test.cjs: the rules with their negatives, and the security
properties the source keeps. The node suites pass, 2160 of 2160. The
templates are not compiled here (no Jade compiler in this sandbox); a Meteor
build checks them. docs/Platforms/FOSS/Weddy/Cloud-Panel.md is the design.
Thanks to xet7 !
The repositories under .tools/ are now grouped by their GitHub owner:
github.com/wekan/* in .tools/w/, github.com/xet7/* in .tools/xet7/ and
github.com/Secretchronicles/* in .tools/Secretchronicles/. build.sh,
build.bat, the release and debug scripts, the tests and the docs looked
for .tools/FerretDB, .tools/wekan.fi, .tools/charts, .tools/node-patches,
.tools/mongo-tools-patches and .tools/TSC, and now use the new places.
ensure_tool_repo takes the owner from the clone URL through a new
tool_repo_dir, so a missing companion repository is cloned into the same
place the scripts read it from. tests/toolsDirectoryRepos.test.cjs runs the
mapping and checks that nothing lands flat in .tools/ any more.
Finding the website checkout again let securityRegressionCoverage compare
the Hall of Fame, which it had been skipping: CreateBleed is published and
is now in the inventory with its unit and UI tests. The exceljs fork test
reads npm-packages/exceljs, the copy WeKan builds with, instead of a clone
under .tools that is not part of the build.
Thanks to xet7 !