Compare commits

...
187 Commits
Author SHA1 Message Date
github-actions[bot] 08143879d1 Bump versions for v13.19 2026-11-19 18:04:43 +00:00
Lauri Ojansivu bf8f45fb5a Prepare v13.19 release 2026-11-19 20:03:38 +02:00
Lauri Ojansivu 84a4334206 Merge remote-tracking branch 'origin/main' 2026-11-19 19:53:24 +02:00
Lauri Ojansivu cc90b358a0 Update WeKan changelog: release builds survive a slow Snap Store and package mirrors.
Thanks to xet7 !
2026-11-19 16:53:46 +02:00
Lauri Ojansivu d49922a6da Release builds: bound the Snap Store processing wait, retry package mirrors.
The v13.18 release run: every wekan and wekan-gantt-gpl snap uploaded,
then sat in the Snap Store's "Status: processing" for hours. snapcraft
polls that with no limit, so GitHub cancelled the jobs at timeout-minutes
(2 h native, 6 h Launchpad). snap-upload-retry.sh now gives one upload
30 minutes (SNAP_UPLOAD_PROCESSING_BUDGET). A revision the store accepted
is left for the store to release to the channels sent with it, with a
warning, instead of uploading it again; an upload cut off before the
store accepted it is retried.

Bun android-arm64 died on a Termux mirror mid-sync ("File has unexpected
size ... Mirror sync in progress?") and Bun freebsd-x64 on an unreachable
FreeBSD package mirror. Termux installs (Bun, Android bundles) and the
i386 libraries of single-file now go through releases/apt-install.sh,
which learned Termux's prefix and lack of sudo. Every BSD VM prepare
retries its package install 5 times and says why when it gives up.

Thanks to xet7 !
2026-11-19 16:53:20 +02:00
github-actions[bot] 985cd8d4a1 Bump versions for v13.18 2026-11-19 01:53:05 +00:00
Lauri Ojansivu 57ebedf392 Prepare v13.18 release 2026-11-19 03:51:21 +02:00
Lauri Ojansivu aa2605b97f Merge remote-tracking branch 'origin/main' 2026-11-19 03:50:51 +02:00
Lauri Ojansivu 5a03999896 Update WeKan changelog: Problems report rows describe one occurrence.
Thanks to xet7 !
2026-11-19 03:34:05 +02:00
Lauri Ojansivu 80fb1c65fc Admin Panel / Problems: a row's address, location and user are one occurrence.
A summary row keeps the LATEST occurrence's username, address, location
and detail, but a field the newest occurrence did not carry was left
from an older one: summaryUpdate only dropped the other address family
from $set, so the old value stayed in the database. Security Report
showed a German IPv4 as "Vancouver, CA" - the location of somebody
else's IPv6 beside it - and JamBleed's "gerald" beside a lockout of
account trottola. The newest occurrence now replaces all the latest
fields and $unset clears the ones it does not carry, in the fold and in
the in-memory fold the legacy migration uses. Existing rows are correct
from their next occurrence on.

Thanks to xet7 !
2026-11-19 03:33:48 +02:00
Lauri Ojansivu b590e17820 Update WeKan changelog: Problems Summary counts in every language.
Thanks to xet7 !
2026-11-19 03:22:38 +02:00
Lauri Ojansivu 7c92cf3298 Admin Panel / Problems / Summary: counts read as sentences, in every language.
"1 new problems" glued a number to a plural label, and Data health's
"Last Run: ... - 8/31" did not say what was counted. Both are now one
translated sentence with the numbers as placeholders: "New problems: 1"
and "Checks with findings: 8 / 31", translated into all 244 locales.
The menu's "Memory Usage" is "Memory usage" like CPU usage and Disk
usage, and broken memory-usage values are corrected: Aymara had an
English wrapper, Latvian had Lithuanian, and Dutch, Frisian, Tagalog,
Tswana, Yoruba and Hawaiian were split or in the wrong word order.

Low confidence: ay, chr, csb, iu, kl, ks, kw, lld, nah, rup, szl, tig,
tlh, uz-AR, ve, ve-PP, vo, wa, wal, zgh.

Thanks to xet7 !
2026-11-19 03:22:10 +02:00
github-actions[bot] 914a79da0b Bump versions for v13.17 2026-11-18 23:54:17 +00:00
Lauri Ojansivu b5495d83d7 Prepare v13.17 release 2026-11-19 01:53:10 +02:00
Lauri Ojansivu ccd4a5a78c Update WeKan changelog: #6927.
Thanks to sro-lbohn and xet7 !
2026-11-19 01:27:41 +02:00
Lauri Ojansivu 0d9c8c1250 Cards of an archived swimlane stay hidden with the Archive sidebar closed.
#6927, a regression of #6659: on a board whose archived swimlane still
holds unarchived cards - archived before #2292 archived cards with their
swimlane, as on a board migrated from WeKan 6.09 - those cards appeared
in the first swimlane, and vanished while the Archive sidebar was open.
The first swimlane surfaces orphaned cards (#6443), and the client could
only exclude swimlanes in its cache; archived swimlanes reach the cache
only with the Archive sidebar.

The board's archived swimlane ids are now published on their own
(boardArchivedSwimlaneIds: one document per board, ids only, read access
as for the board) into a client-only collection, and
Lists.orphanedCardsSwimlaneIds excludes them. Nothing that lists
swimlanes starts showing archived ones, and the cards are not changed:
moving or archiving them was what brought old cards back before
(swimlane-structure, 2026-08-13).

tests/archivedSwimlaneCards6927.test.cjs replays the reporter's board;
archived-swimlane-cards-6927.e2e.js checks it with the Archive sidebar
open and closed.

Thanks to sro-lbohn, hmeunier95 and xet7 !

Fixes #6927.
2026-11-19 01:27:40 +02:00
Lauri Ojansivu f413e53835 Update WeKan changelog: Admin Panel structure and menu docs.
Thanks to xet7 !
2026-11-19 01:23:10 +02:00
Lauri Ojansivu a8fd080bc8 Docs mirror the Admin Panel and the menus: a page for every menu entry.
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 !
2026-11-19 01:22:22 +02:00
Lauri Ojansivu e1a053d059 Admin Panel: one question per tab - Settings gains Appearance, Features, Feature profiles, Security, Activities and Delete.
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 !
2026-11-19 01:22:13 +02:00
Lauri Ojansivu 58158ca9ab Translate shared authentication messages into Maithili
Technical authentication terminology is lower confidence.
2026-11-19 01:10:01 +02:00
Lauri Ojansivu 4a8fb736e5 Translate shared authentication messages into Bhojpuri
Technical authentication terminology is lower confidence.
2026-11-19 01:09:20 +02:00
Lauri Ojansivu 4fb99602b6 Translate shared authentication messages into Sindhi
Technical session terminology is lower confidence.
2026-11-19 01:08:32 +02:00
Lauri Ojansivu 31ea58c408 Translate shared authentication messages into Punjabi 2026-11-19 01:07:47 +02:00
Lauri Ojansivu ea680e5389 Translate shared authentication messages into Telugu 2026-11-19 01:07:01 +02:00
Lauri Ojansivu 1eb00ff8cb Translate shared authentication messages into Odia
Technical session and administrator terminology is lower confidence.
2026-11-19 01:06:18 +02:00
Lauri Ojansivu 31dafef73d Translate shared authentication messages into Assamese
Technical session and administrator wording is lower confidence.
2026-11-19 01:05:24 +02:00
Lauri Ojansivu 907e0bd89d Translate shared authentication messages into Algerian Arabic
Technical session and administrator terminology is lower confidence.
2026-11-19 01:04:43 +02:00
Lauri Ojansivu fb7ab1dc2d Translate shared authentication messages into Moroccan Arabic 2026-11-19 01:04:01 +02:00
Lauri Ojansivu 5539e38242 Translate shared authentication messages into Egyptian Arabic 2026-11-19 01:03:21 +02:00
Lauri Ojansivu d301fd39f8 Translate shared authentication messages into Japanese hiragana 2026-11-19 01:02:42 +02:00
Lauri Ojansivu 8cab0730b4 Reuse Simplified Chinese authentication messages in Mandarin catalog 2026-11-19 01:01:57 +02:00
Lauri Ojansivu daedcf7eee Translate shared authentication messages into Cantonese 2026-11-19 01:01:18 +02:00
Lauri Ojansivu cdbf67d359 Translate shared authentication messages into Hawaiian
Technical authentication and session terminology is lower confidence.
2026-11-19 01:00:37 +02:00
Lauri Ojansivu 71acbba05c Translate shared authentication messages into Fijian
Technical authentication, domain and session terms are lower confidence.
2026-11-19 00:59:46 +02:00
Lauri Ojansivu c536867b7f Translate shared authentication messages into Tongan
Technical session terminology is lower confidence.
2026-11-19 00:59:02 +02:00
Lauri Ojansivu dfc51e0eae Translate shared authentication messages into Samoan
Technical authentication and session terminology is lower confidence.
2026-11-19 00:58:14 +02:00
Lauri Ojansivu 1b3b074bf1 Translate shared authentication messages into Malagasy
Technical setup and session terminology is lower confidence.
2026-11-19 00:57:26 +02:00
Lauri Ojansivu ec2ea4ca31 Translate shared authentication messages into Igbo
Technical authentication and session terminology is lower confidence.
2026-11-19 00:55:57 +02:00
Lauri Ojansivu 793683c4c7 Translate shared authentication messages into Yoruba
Technical authentication and session terminology is lower confidence.
2026-11-19 00:55:17 +02:00
Lauri Ojansivu 4e16699fe4 Translate shared authentication messages into Uyghur
Technical session and administrator terminology is lower confidence.
2026-11-19 00:54:28 +02:00
Lauri Ojansivu ad18fe00e9 Translate shared authentication messages into Bashkir
Technical authentication terminology is lower confidence.
2026-11-19 00:53:43 +02:00
Lauri Ojansivu bb87b93c6e Translate shared authentication messages into Tatar
Technical authentication terminology is lower confidence.
2026-11-19 00:53:04 +02:00
Lauri Ojansivu 298f68dc40 Translate shared authentication messages into Turkmen 2026-11-19 00:52:26 +02:00
Lauri Ojansivu 5b8341e014 Translate shared authentication messages into Tok Pisin
Technical authentication and session terminology is lower confidence.
2026-11-19 00:51:42 +02:00
Lauri Ojansivu 96b34e8d9b Translate shared authentication messages into Neapolitan
Authentication and session terminology is lower confidence.
2026-11-19 00:50:42 +02:00
Lauri Ojansivu 2059ef7612 Translate shared authentication messages into Sardinian
Technical authentication and session terminology is lower confidence.
2026-11-19 00:49:59 +02:00
Lauri Ojansivu 4810de82d6 Translate shared authentication messages into Sicilian
Technical authentication and session terminology is lower confidence.
2026-11-19 00:49:21 +02:00
Lauri Ojansivu b015f76225 Translate shared authentication messages into Asturian and Aragonese
Aragonese technical terminology is lower confidence.
2026-11-19 00:48:48 +02:00
Lauri Ojansivu 18e04f4f02 Translate shared authentication messages into Kurmanji and Sorani
Technical authentication and session terminology is lower confidence.
2026-11-19 00:48:06 +02:00
Lauri Ojansivu 8b7462a1c5 Translate shared authentication messages into Pashto
Technical session and administrator terminology is lower confidence.
2026-11-19 00:47:08 +02:00
Lauri Ojansivu 7c0f0a2e91 Translate shared authentication messages into Shona
Technical domain and session terms are lower confidence.
2026-11-19 00:46:27 +02:00
Lauri Ojansivu 1db8366a37 Translate shared authentication messages into Xhosa
Technical administrator and session terms are lower confidence.
2026-11-19 00:45:46 +02:00
Lauri Ojansivu 3d42a1101c Translate shared authentication messages into Zulu
Technical authentication and administrator terminology is lower confidence.
2026-11-19 00:45:08 +02:00
Lauri Ojansivu 65b6eed3b7 Translate shared authentication messages into Tagalog 2026-11-19 00:44:26 +02:00
Lauri Ojansivu 46adbd0608 Translate shared authentication messages into Papiamento
Technical authentication and session terms are lower confidence.
2026-11-19 00:43:51 +02:00
Lauri Ojansivu ffd5c89b6d Translate shared authentication messages into Romansh
Technical session terminology is lower confidence.
2026-11-19 00:43:14 +02:00
Lauri Ojansivu b094d53ff8 Translate shared authentication messages into Māori
Technical enrollment and session terminology is lower confidence.
2026-11-19 00:42:40 +02:00
Lauri Ojansivu bbc988b1a8 Translate shared authentication messages into Amharic
Session terminology is lower confidence.
2026-11-19 00:41:59 +02:00
Lauri Ojansivu 4670cf781c Translate shared authentication messages into Yiddish
Technical enrollment terminology is lower confidence.
2026-11-19 00:41:04 +02:00
Lauri Ojansivu 4f5aa339b3 Translate shared authentication messages into Breton and Occitan
Breton technical terminology is lower confidence.
2026-11-19 00:40:26 +02:00
Lauri Ojansivu 4992f9d203 Translate shared authentication messages into Luxembourgish and West Frisian
Enrollment terminology is lower confidence in both languages.
2026-11-19 00:39:33 +02:00
Lauri Ojansivu e812fe45a7 Translate shared authentication messages into Haitian Creole and Javanese
Javanese enrollment terminology is lower confidence.
2026-11-19 00:38:40 +02:00
Lauri Ojansivu c0ff740263 Translate shared authentication messages into Somali and Hausa
Session and enrollment terminology is lower confidence.
2026-11-19 00:37:57 +02:00
Lauri Ojansivu 05e95004b5 Translate shared authentication messages into Latin and Corsican
Technical terminology is lower confidence in both languages.
2026-11-19 00:37:05 +02:00
Lauri Ojansivu cbd27a2c8c Translate shared authentication messages into Khmer and Burmese
Session terminology in Khmer and Burmese is lower confidence.
2026-11-19 00:36:18 +02:00
Lauri Ojansivu 7f946df622 Localize shared authentication messages in nine more catalogs 2026-11-19 00:35:25 +02:00
Lauri Ojansivu caf5e67842 Translate shared authentication messages into Nepali, Urdu and Sinhala 2026-11-19 00:34:34 +02:00
Lauri Ojansivu c172b6639d Translate shared authentication messages into Gujarati, Kannada, Malayalam and Marathi 2026-11-19 00:33:40 +02:00
Lauri Ojansivu 383fc6de98 Translate shared authentication messages into Mongolian and Tajik 2026-11-19 00:32:28 +02:00
Lauri Ojansivu 79d7141e09 Translate shared authentication messages into Kazakh, Kyrgyz and Uzbek 2026-11-19 00:31:39 +02:00
Lauri Ojansivu 6ae104c686 Translate shared authentication messages into Estonian and Faroese 2026-11-19 00:31:11 +02:00
Lauri Ojansivu 38b28fb3e3 Translate shared authentication messages into Chinese 2026-11-19 00:31:11 +02:00
Lauri Ojansivu e2c8e58c20 Localize shared authentication messages in 34 regional catalogs 2026-11-19 00:31:10 +02:00
github-actions[bot] 197725ae19 Bump versions for v13.16 2026-11-18 22:28:18 +00:00
Lauri Ojansivu 59f3e73117 Prepare v13.16 release 2026-11-19 00:27:22 +02:00
Lauri Ojansivu 39bb89c4a7 Add shared WeKan enrollment and registration keys 2026-11-19 00:27:08 +02:00
Lauri Ojansivu a833d95adc Use WeKan as the translation source for its prototypes 2026-11-19 00:21:55 +02:00
Lauri Ojansivu 5285ca918a Update WeKan changelog: swap alone is not high RAM usage.
Thanks to xet7 !
2026-11-19 00:21:44 +02:00
Lauri Ojansivu cfd9a62466 Swap alone is not high RAM usage, and resource monitors are not named like vulnerabilities.
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 !
2026-11-19 00:21:33 +02:00
Lauri Ojansivu 1293dc6b45 Move feature profiles (#6837) from TODO.md to the changelog.
TODO.md keeps only the WebKit stage, which needs a host outside the
Flatpak sandbox.

Thanks to mimZD and xet7 !
2026-11-19 00:02:07 +02:00
Lauri Ojansivu fc21b0b177 Feature profiles: an administrator hides features from chosen users, teams and organizations.
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.
2026-11-19 00:01:42 +02:00
Lauri Ojansivu 2ea288d7c5 Move List Sync's rule replay skip from TODO.md to the changelog.
Thanks to xet7 !
2026-11-18 23:46:15 +02:00
Lauri Ojansivu a0f3681961 List Sync's rule replay skips an action into a list that refuses the actor's role.
Decided by the maintainer on 2026-11-18 (TODO.md). The ordinary rules
engine already skips such an action; the journaled List Sync replay
(server/notifications/storedRulePlans.js) still wrote with board write
access only.

Each list-writing runner - move, move to another board, move all,
move all to another board, copy, link, create card, sort list and
archive - now decides before it saves its command: a list refusing the
actor's role (#4527) records a durable skip (listSyncRuleListSkips) and
the runner returns the invocation id, which executeRulePlan confirms
like any finished action, so the rest of the plan runs. A replay reads
the saved skip first, so it never re-decides; a saved command is never
skipped and a skipped action never gets a command. The skip shows in
Admin Panel / Problems as ListLockRule (detected, low).

tests/listSyncRuleListSkip.test.cjs runs the skipper and pins every
runner's order.

Thanks to xet7 !
2026-11-18 23:46:00 +02:00
Lauri Ojansivu 96430d4679 Move list and swimlane changes and rule actions from TODO.md to the changelog.
TODO.md keeps the List Sync replay follow-up and #6837.

Thanks to xet7 !
2026-11-18 23:08:19 +02:00
Lauri Ojansivu ee24453dcb A rule action into a list that refuses the triggering user's role is skipped.
Decided by the maintainer on 2026-11-18 (TODO.md). A rule's move, archive,
unarchive, create-card, copy, link, sort-list and move-all-cards actions
checked only board write access. Each now asks the lists it writes in as
the user who triggered the rule (#4527); a refusing list skips that
action, and the rest of the rule still runs. The skip shows in Admin
Panel / Problems as ListLockRule (authz.rule-list-locked, detected, low,
never disables): it is a rule meeting a locked list, not an attack.

List Sync's journaled rule replay is not changed yet - a skip there needs
a receipt of its own - and stays in TODO.md.

tests/listLockRules.test.cjs runs the check and copyRuleCard against a
locked list and pins every action.

Thanks to xet7 !
2026-11-18 23:08:06 +02:00
Lauri Ojansivu 3202a1d7ac A list's role exception also refuses deleting, archiving or moving it, and its swimlane.
Decided by the maintainer on 2026-11-18 (TODO.md). Deleting, archiving,
restoring or moving a list, and deleting, archiving or moving a
swimlane, does the same to the cards in it, so a list that refuses a
role write access (#4527) now refuses those too:

- lists.softRemove, lists.restore and moveList answer not-authorized;
- the REST list DELETE, archive, unarchive and move, and the REST
  swimlane DELETE, answer 403, recorded as ListLockBleed;
- moveSwimlane is refused when a list holding its cards, or bound to
  it, refuses the role (swimlaneRefusingListIds);
- client writes meet new Lists and Swimlanes deny rules, and the list
  menu no longer offers Archive list or Archive all cards in such a list.

Renaming, recolouring and reordering are not refused, and board admins
are never restricted.

tests/listLockStructure.test.cjs runs the swimlane gate and pins every
path; list-lock-bulk.e2e.js replays the REST cases. Sandboxed route
tests get a pass-through gate.

Thanks to xet7 !
2026-11-18 23:08:06 +02:00
Lauri Ojansivu 16f208cb47 Move dependency lines and list exceptions from TODO.md to the changelog.
Thanks to xet7 !
2026-11-18 22:57:45 +02:00
Lauri Ojansivu da6d9d39b8 Dependency lines follow the card's list role exception.
Decided by the maintainer on 2026-11-18 (TODO.md): a list that refuses a
role write access (#4527) refuses that role's dependency lines on its
cards too, since a line is stored on its source card. setBoardDependency
and removeBoardDependency answer not-authorized, the REST dependency
routes answer 403 recorded as ListLockBleed, and importBoardDependencies
skips such lines. Board admins and site admins are not restricted, as
before.

tests/listPermissions.test.cjs no longer exempts the dependency routes
and follows the access helpers a route awaits;
tests/listLockDependencies.test.cjs pins DDP and the import, and
list-lock-bulk.e2e.js replays it over REST.

Thanks to xet7 !
2026-11-18 22:57:33 +02:00
Lauri Ojansivu 941e1794f7 TODO.md: record the maintainer's decisions on list exceptions and #6837.
Thanks to xet7 !
2026-11-18 22:56:23 +02:00
Lauri Ojansivu d2966d0624 Verify untitled card links on WeLite boards 2026-11-18 22:35:54 +02:00
Lauri Ojansivu 26c457b18e TODO.md: #6834 is closed.
The maintainer closed it on 2026-11-01, asking the reporter to upgrade;
the header wrapping did not reproduce on current code and no reply came.
Nothing changed in WeKan for it, so there is no changelog entry.

Thanks to mimZD and xet7 !
2026-11-18 22:33:08 +02:00
Lauri Ojansivu 879627c641 Move TODO Later from the changelog to TODO.md.
The changelog now says only what changed. What is not done yet, with
why, is in TODO.md at the repository root; Status links it. When an
item is done it is removed from TODO.md and its entry goes into the
Upcoming section of CHANGELOG-big.md. CLAUDE.md and AGENTS.md say so,
tests/changelogFormat.test.cjs checks the changelog no longer carries
TODO Later, and tests/todoFile.test.cjs checks TODO.md's shape.

TODO.md also records three maintainer decisions left open by
ListLockBulkBleed: whether per-list role exceptions should apply to
dependency lines, to the rules engine's own actions, and to deleting,
archiving or moving whole lists and swimlanes.

Thanks to xet7 !
2026-11-18 22:32:52 +02:00
Lauri Ojansivu ab10ade956 Update WeKan changelog: ListLockBulkBleed, History audit memory, scheduled rules, clearing card text.
Also corrects the Excel export spec's link to its rebased commit.

Thanks to immanuwell, AhmedLukman and xet7 !
2026-11-18 22:26:22 +02:00
Lauri Ojansivu 7459c5bde6 The History integrity audit streams each board instead of loading it whole.
Production log (v13.13): "JavaScript heap out of memory" twice, 42 and
74 seconds after the hourly History integrity audit started (its
changeHistory distinct is in the MongoDB log at 03:00:00 and 05:00:00),
both in the first hourly run of a freshly started process. The audit
fetched each board's whole History - every row with its full previous
and new content - and verified the array.

historyVerifier checks one row at a time and keeps only hashes, the first
child of each predecessor, root counts and small summaries; the audit
streams each board through a cursor with a bounded batch, pausing while
the CPU is busy. verifyHistoryRows runs on it and returns exactly what
it did. tests/historyIntegrityStreaming.test.cjs compares both on chains
with forks, a second root, a tampered and an orphan row, and fails if
the audit fetches a board whole.

Thanks to xet7 !
2026-11-18 22:25:34 +02:00
Lauri Ojansivu f23695cc1b Scheduled rules act as the board's admin, so their created cards have an author.
Production log (v13.13): "scheduledRules: error running trigger ...
User ID is required in cards insertAsync" on every run. Scheduled rules,
auto-archive and attachment retention acted as board.createdBy, but the
Boards schema has no createdBy, so it was undefined on every board: a
scheduled rule ran as nobody and its "create card" action always failed.

models/lib/boardActor.js names the board's first active admin, else its
first active member. The rule's createCard action also passes its acting
user as the card's author, since a scheduled run has no method user for
the schema's autoValue. tests/boardActor.test.cjs scans the tree so that
nothing reads board.createdBy again.

Thanks to xet7 !
2026-11-18 22:25:34 +02:00
Lauri Ojansivu ba3d94390b ListLockBulkBleed: bulk and server-side card writes ask the list's role exception.
GHSA-83w9-74mx-7v83. A board admin can refuse a role write access in one
list (#4527, roleExceptions). REST DELETE /api/boards/:boardId/cards/bulk
and POST /api/boards/:boardId/cards/labels take their cards from the
body, so no URL names a list, and asked only for board write access; the
methods archiveSelectedCards, copyCard and createLinkedCard write from
server code, past the Cards allow/deny rules. A normal member the list
refused could delete, relabel and archive its cards and copy or link new
cards into it.

- The bulk routes read every card and ask each list before the first
  write (assertCardListsNotRefused): any refusal is a 403 and nothing
  changes, recorded in Admin Panel / Problems as ListLockBulkBleed
  (authz.list-locked-bulk, medium). Each removal and relabel is keyed on
  the list that was checked.
- The methods refuse with not-authorized (assertListsWritable), not
  recorded: Copy Card and Multi-Selection reach them in ordinary use.
- The same shape, fixed with the same check: createBoardFromCard,
  addSubtaskCard, createCardWithDueDate (which also did not check that
  the list is on the board), the iCalendar import over DDP and REST,
  sending and receiving board email, vcsCreateIssue, moveBoardObjects,
  History's undo/redo/Restore, position history undo/redo of a card,
  renameAttachment, the scoped import and a card's rule button.
  Dependency lines keep their own board-wide rule.

tests/listLockBulkBleed.test.cjs runs the gate on the reporter's board
and pins every path; tests/playwright/specs/list-lock-bulk.e2e.js replays
the proof of concept. Older guards that pinned the previous shape are
updated with the reason.

Thanks to immanuwell and xet7 !
2026-11-18 22:25:34 +02:00
Lauri Ojansivu 22dae19a64 Exercise REST card title edits on WeLite boards 2026-11-18 22:24:06 +02:00
Lauri Ojansivu 74dd0b705e Resolve sibling helper requires in the attachment cleanup test sandbox.
db.js now requires ./welite-auth, which the vm sandbox resolved against
the test file instead of the helpers directory.

Thanks to xet7 !
2026-11-18 21:39:15 +02:00
Lauri Ojansivu aacb2fd4d6 Clearing a card title or description can be undone and redone.
Follow-up to PR #6926. Clearing a value is an edit recorded in History,
not a deletion, so Admin Panel / Problems / Delete has no part in it and
the old value stays restorable. collection2's default clean removes ''
from $set and then throws "your modifier is now empty", so:

- History's redo and Restore of a cleared title or description threw,
  while undo worked. applyFieldContent now writes the recorded value back
  exactly (removeEmptyStrings and trimStrings off).
- The card details title and description clear, and the board
  description clear, pass removeEmptyStrings: false.
- REST card PUT always passes removeEmptyStrings: false for title and
  description: a title of only spaces was trimmed to '' and then removed,
  a 500, and the #6877 description clear had no option at all.

tests/emptyStringClearWrites.test.cjs replays undo/redo/Restore through a
collection2-like clean and pins the options at every write;
tests/playwright/specs/card-clear-undo-redo.e2e.js clears in the card
details and over REST, then undoes and redoes.

Thanks to AhmedLukman and xet7 !
2026-11-18 21:39:15 +02:00
Lauri Ojansivu d1e0bae6a5 Update WeKan changelog: Upcoming release.
Thanks to AhmedLukman and xet7 !
2026-11-18 21:27:31 +02:00
Lauri Ojansivu 320a3ca867 Test card Excel export with only Description or only Labels selected.
The browser-level regression test for PR #6925: drives the real
exportExcel route with fields=description and fields=labels, and checks
that each workbook carries the selected field and not the other one or
the board title.

Thanks to AhmedLukman and xet7 !
2026-11-18 21:27:31 +02:00
Lauri Ojansivu 58ba1e4b3b Merge pull request #6926 from AhmedLukman/codex/rest-card-empty-title
Allow clearing card titles through REST
2026-11-18 21:27:15 +02:00
Lauri Ojansivu ba9504d6db Verify regional Arabic attachment captions on WeLite 2026-11-18 21:14:37 +02:00
Lauri Ojansivu 6f7292cffd Verify Arabic webhook field captions on WeLite 2026-11-18 21:14:37 +02:00
Lauri Ojansivu 8c1152f234 Verify regional Arabic captions in WeLite People tables 2026-11-18 21:14:37 +02:00
Lauri Ojansivu f1fe22ac16 Verify RTL People table captions on WeLite 2026-11-18 21:14:37 +02:00
Lauri Ojansivu 333928f123 Allow time for the WeLite attachment browser workflow 2026-11-18 21:14:37 +02:00
Lauri Ojansivu bd6b00c5f4 Reuse the browser session in the WeLite attachment cascade spec 2026-11-18 21:14:37 +02:00
Lauri Ojansivu c5344761d8 Verify Finnish attachment preview in WeLite 2026-11-18 21:14:37 +02:00
Lauri Ojansivu 075e6dbe73 Verify both export links on the WeLite board 2026-11-18 21:14:37 +02:00
Lauri Ojansivu f34fee6582 Run upstream webhook settings cases on WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu e30c439fa7 Exercise targeted WeLite browser session revocation 2026-11-18 21:14:36 +02:00
Lauri Ojansivu 6bf2d53d75 Run upstream custom-field lifecycle cases on WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu b6bc2b200c Run Version Control Attachments workflow on native WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu c060c6d2db Verify direct attachment removal in native WeLite Chromium 2026-11-18 21:14:36 +02:00
Lauri Ojansivu 7c3b798a1d Verify native attachment rename and reject missing form token 2026-11-18 21:14:36 +02:00
Lauri Ojansivu 26e27f62c4 Run the upstream card attachment cascade spec on WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu f1adc7982e Run the upstream dropdown deletion spec on native WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu b8fd94a7e7 Run the upstream dropdown rename spec on native WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu 8abb9504bb Run upstream assignment removal REST cases on native WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu a9059b7b15 Seed native Playwright credentials before API token use 2026-11-18 21:14:36 +02:00
Lauri Ojansivu 399a8defec Run the upstream write-route scope spec on native WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu ede46c7a98 Run the upstream checklist REST spec on native WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu e4115e6890 Run the upstream user update REST spec on native WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu 72ee1c8b23 Run the upstream People features spec on native WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu 2033c177ce Run the upstream overtime REST spec on native WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu db3f489ab2 Run the upstream subtask REST spec on native WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu 11fc468ff7 Run the upstream archive and restore spec on native WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu 5f06b28aef Run native board sorting through the upstream REST spec 2026-11-18 21:14:36 +02:00
Lauri Ojansivu 049b628a03 Exercise the ownership REST spec against native WeLite 2026-11-18 21:14:36 +02:00
Lauri Ojansivu 6d8d2a7699 Merge pull request #6925 from AhmedLukman/codex/card-xlsx-optional-context
Fix card Excel exports when board information is omitted
2026-11-18 21:12:06 +02:00
Ahmed Lukman 79a98822cb Report unmatched REST card title updates 2026-11-18 20:05:18 +03:00
Ahmed Lukman c59c751547 Allow clearing card titles through REST 2026-11-18 19:31:45 +03:00
github-actions[bot] c739eaeeee Bump versions for v13.15 2026-11-18 10:26:34 +00:00
Lauri Ojansivu ac365ef116 Prepare v13.15 release 2026-11-18 12:25:45 +02:00
Ahmed Lukman 997c6d88ad Fix card Excel exports when board information is omitted
Allow the shared card export builder to read titles from optional board, list and swimlane records. Cover description-only and labels-only field selections.
2026-11-18 11:59:44 +03:00
Lauri Ojansivu 5f92c8efec Expect 404 for wrong-board custom field updates 2026-11-18 10:12:04 +02:00
Lauri Ojansivu 320e98269e Merge remote-tracking branch 'origin/main' 2026-11-18 08:45:59 +02:00
Lauri Ojansivu dc80a93041 Tests: RaceBleed is in the security regression inventory, with its two suites.
Thanks to xingmuse and xet7 !
2026-11-18 03:49:12 +02:00
Lauri Ojansivu bf70908c0a Updated ChangeLog.
Thanks to xingmuse and xet7 !
2026-11-18 03:48:46 +02:00
Lauri Ojansivu baaeea27e3 REST API: a handler's Meteor "not-found" error is a 404, not a 500.
httpStatusForError knew only 'NotFound', while about two hundred throw sites
in server/ spell it Meteor's way - 'not-found', 'board-not-found',
'list-not-found', 'user-not-found' and the rest. So DELETE of a missing
swimlane, and a board-member add naming nobody, answered 500 "Internal
server error" on a real server, while tests/restWriteRoutes404.test.cjs,
which stubs the helper, saw the 404 - found by
tests/playwright/specs/rest-write-routes-404.e2e.js while testing RaceBleed.

Any error name that is or ends in "not-found" is now a 404 with its message;
everything unknown is still a 500 that carries no detail.
tests/restNotFoundStatus.test.cjs runs the real helper, and fails on any
not-found spelling in server/ that it would not map.

Thanks to xet7 !
2026-11-18 03:47:53 +02:00
Lauri Ojansivu c7a496c9cf Security: RaceBleed - a card's children are destroyed only for a card whose own removal happened.
GHSA-3vjg-3p4q-8fwh. The REST card DELETE looked the card up on the board
the caller was authorised for, destroyed its checklists, checklist items,
comments, attachments and subcards by cardId, and removed the card itself
last, keyed on that board and list. A move to another board landing in
between left the card alive on a board the deleter cannot read, stripped of
every child, with both requests answering 200 (CWE-367). Every hooked
removal had the same shape: collection-hooks runs Cards.before.remove (where
the cascade was) and then removes by the caller's original selector - by
swimlane, delete batch or parent - which a moved card no longer matches. The
custom-field link clean-up did the same to the cards linked to it.

The card document is now the claim (models/lib/claimedCardRemoval.js): the
single and bulk REST deletes remove the card first and cascade only when
that removal matched, and the hooked removals cascade from Cards.after.remove
only when the card is really gone. A list deletion removes a card only while
it is still in that list. The REST board move that loses to a delete is a
404 instead of a 500 from cardMove.

A delete that lost the race, or arrived after the card was moved away from
the named board, is refused and recorded in Admin Panel / Problems as
RaceBleed (authz.card-delete-race, medium, never disables the account): a
stale view is not an attack, and PurgeBleed's critical record used to
disable the member who deleted a card somebody had just moved.

tests/claimedCardRemoval.test.cjs replays the reported race and scans
server/ for any cascade before or without the card's removal;
tests/playwright/specs/race-bleed.e2e.js races 12 moves against deletes
and checks that a surviving card always keeps its checklist.

Thanks to xingmuse and xet7 !
2026-11-18 03:43:25 +02:00
github-actions[bot] 5be568495e Bump versions for v13.14 2026-11-16 21:13:02 +00:00
Lauri Ojansivu ebcdf327b0 Prepare v13.14 release 2026-11-16 23:12:07 +02:00
Lauri Ojansivu e3da773d03 Shared list headers guard expects the !important hiding rule.
The #2805 guard still pinned a plain `display: none`, which the #6902 fix
made `!important` because the desktop list header's
`display: block !important` overrode it. The guard now says why.

Thanks to xet7 !
2026-11-16 20:19:19 +02:00
Lauri Ojansivu b35184d487 VSCodium sandbox: allow the host's Docker through flatpak-spawn --host.
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 !
2026-11-16 20:10:25 +02:00
Lauri Ojansivu db3b12fac2 Merge remote-tracking branch 'origin/main' 2026-11-16 20:07:31 +02:00
Lauri Ojansivu a34beaa62b Updated ChangeLog.
Thanks to xet7 !
2026-11-16 16:46:36 +02:00
Lauri Ojansivu 138f727ebb Card shortcuts open only their popup.
d, Shift+M and Shift+C on a hovered or selected minicard opened the card
first, and Shift+M / Shift+C then opened the card's hamburger menu and
clicked its item: card, menu and popup for one key. Now the Due date, Move
card or Copy card popup opens by itself next to the minicard, as a click on
a minicard's date or label opens only its popup, and the card stays closed.
On an opened card Move / Copy open next to its hamburger without showing the
menu; d there still clicks the card's own Due date control.

The popup is opened directly, so client/lib/cardShortcutPopup.js applies the
conditions the controls a click would use are rendered under: the board
allows due dates and the user may modify the card (a Worker only edits an
existing date), Move card for a board admin, Copy card for a member who is
not a Worker, both only with cardMenuWrites. Without them nothing opens.
tests/cardShortcutPopup.test.cjs drives the rules and ties each one to its
template condition; the browser specs check the card stays closed and no
menu is shown, and that a non-admin and disabled shortcuts open nothing.
The help-list check matched "Move Card to Archive" too and now matches the
action text exactly.

Thanks to mimZD and xet7 !

Fixes #6924.
2026-11-16 16:46:06 +02:00
Lauri Ojansivu 39ee1d9512 One shared list header row hides the other swimlanes' list headers.
The rule hiding them was `display: none`, and the desktop list header layout
sets `display: block !important` (lists/list.css, boardHeader.css); a plain
declaration loses to an !important one, so every swimlane kept its headers
and tests/playwright/specs/shared-list-row-6902.e2e.js failed. The rule is
!important now, and its selector outranks those. tests/sharedListRow6902.test.cjs
finds every !important display rule on a .list-header in the client CSS and
requires the hiding rule to outrank it (verified to fail on the old rule).

Thanks to mimZD and xet7 !
2026-11-16 16:46:06 +02:00
Lauri Ojansivu b05972c4c8 A checklist folded on a minicard stays folded: no publication sends the current user a partial profile.
The fold was stored, and half a second later the checklist unfolded again.
DDP merges only top-level fields, and Meteor re-runs named subscriptions
before the accounts publication of the whole profile on every login, a
reconnect included. userDesktopDragHandles sent the current user
{ profile: { showDesktopDragHandles } }, and user-miniprofile, user-search,
notificationUsers, the card search and report, the boards report, People,
the impersonation report and the Chat view's comment authors sent a few
profile.* fields that could include the current user. When one of them won,
the client's profile shrank to those fields until a reload, and every
preference in it went back to its default; #6691 had found the same for the
board view and fixed only that one.

userDesktopDragHandles now publishes the preference under its own top-level
field, as userBoardView does, and utils.js reads it when the profile has
none. Every other publication leaves the current user out
(server/lib/notCurrentUser.js); their own document is published in full
already, and user-admin now also publishes createdAt, loginDisabled,
lastConnectionDate and importUsernames for the user's own row on the admin
pages.

tests/noNarrowProfileForCurrentUser6919.test.cjs finds every users query
with profile subfields in a server file that publishes and requires it to
leave the current user out (verified to fail when one does not).
tests/playwright/specs/minicard-checklist-collapse-6919.e2e.js folds and
unfolds a minicard checklist in Persian after a page load and after a
reconnect, on the reporter's card, a second checklist, a linked card, a user
with 300 earlier folds and both swimlanes of a shared list header row, and
checks the fold survives the server's answer, in the database and on the
client. Before the fix 4 of 24 reconnect runs unfolded; with it 24 of 24 and
the whole spec pass in Chromium.

Thanks to mimZD and xet7 !

Fixes #6919.
2026-11-16 16:46:06 +02:00
Lauri Ojansivu 495a6faa63 Source test mode starts again: meteor/<package>/main resolves.
build.sh's source test mode (scripts/dev-source) stopped at startup with
"Cannot find module 'meteor/aldeed:collection2/main'". server/main.js loads
collection2's main module before the models (2699f4deea), and the source
runtime resolved only a bare meteor/<package>. It now maps
meteor/<package>/main to the same package exports, which image.load has
already run. tests/devSourceMainModule.test.cjs checks every such import in
the server entry resolves, and that other sub-paths are not taken for it.

Thanks to xet7 !
2026-11-16 16:46:06 +02:00
Lauri Ojansivu 8eff8bb442 Merge pull request #6922 from AhmedLukman/codex/fix-dropdown-option-rename
Fix REST dropdown option renaming
2026-11-16 15:21:52 +02:00
Ahmed Lukman 00b0431685 Fix REST dropdown option renaming
Use an explicit array index when renaming a dropdown option so schema
validation and protected-field checks can preview the update. Match the
option ID at that index to avoid renaming a sibling after a concurrent
removal or reorder, and return 404 when the update no longer matches.

Add handler and browser regressions for persisted names, stable selections,
encoded IDs, missing targets, authorization and protected-field restrictions.

Thanks to AhmedLukman and xet7 !
2026-11-16 15:11:51 +03:00
Lauri Ojansivu a364e75025 Updated ChangeLog.
Thanks to xet7 !
2026-11-16 13:58:38 +02:00
Lauri Ojansivu 040d853c8e RedirectBleed hardening: a direct client write of an avatar URL follows setAvatarUrl's rule.
setAvatarUrl refuses javascript:, file:, data:text/html and every scheme but
http(s), data:image and local paths, but the Users allow rule permits every
profile.* field, so Users.update({$set: {'profile.avatarUrl': ...}}) from the
browser console stored what the method refuses. Not exploitable as reported:
the URL is rendered only as an <img src>, and the server fetches it only
through fetchSafe (http/https). The rule is now models/lib/avatarUrlScheme.js,
used by both avatar methods and by a Users deny rule, which logs the refused
write to Admin Panel / Problems as file.avatar-url. No WeKan client code
writes the field directly, which the test checks.

Verified while checking meifukun's GHSA-g98f-44gc-hqcc, GHSA-x6fh-wrr5-3426,
GHSA-28hr-j65r-grj2, GHSA-mrhx-8xm7-chrq and GHSA-83qj-w8mp-w4qf against the
current code: all five were already fixed (tests/securityMeifukun.test.cjs).

Thanks to meifukun and xet7 !
2026-11-16 13:54:08 +02:00
Lauri Ojansivu 79676b3790 Description editor shows no placeholder text instead of "comment-placeholder".
i18next 27 (#6915, shipped in v13.13) changed returnEmptyString to default
false, so an empty translation falls back like a missing one, to its key.
en.i18n.json keeps comment-placeholder and eight Blockly suffixes empty on
purpose, so the description and comment editors showed the text
"comment-placeholder". TAPi18n.init() now sets returnEmptyString: true, which
is the v26 behaviour; no language has an empty value where English has text,
so nothing that should fall back to English goes blank.

lld, lb, haw and sc had text for the empty English source ("Optioun: ",
"Ma ka ʻōlelo Hawaiʻi: "), which is not a translation of anything; they are
empty now like every other language.

tests/i18nEmptyString.test.cjs runs the real __() with the init() options
read from tap.js (verified to fail without the fix on i18next 27.1.1), and
checks no language has a blank value where English has text. The mocha suite
and the description Playwright spec check the placeholder is empty.

Thanks to brlin-tw and xet7 !

Fixes #6921.
2026-11-16 13:47:58 +02:00
Lauri Ojansivu 5ec3aaf85f Guard follows the merged dependabot update: freebsd-vm 1.6.0.
Dependabot moved bsd.yml's FreeBSD VM to v1.6.0 (#6907), and
tests/bsdBundles.test.cjs requires the same commit as node-patches, which
builds node-freebsd-x64 in that VM. node-patches now uses v1.6.0 too, so the
guard pins its new commit.

Thanks to xet7 !
2026-11-16 13:43:18 +02:00
Lauri Ojansivu cc302acdd1 Merge pull request #6920 from AhmedLukman/codex/fix-card-attachment-cascade
Soft-delete attachments when removing their card
2026-11-16 13:32:22 +02:00
Lauri Ojansivu 77c22918d7 Merge pull request #6918 from AhmedLukman/codex/fix-attachment-rename-validation
Keep renamed upload paths consistent before validation
2026-11-16 13:31:46 +02:00
Ahmed Lukman 1051265fc8 Cover attachment cleanup through the card delete menu
Upload attachments through the browser and delete their card through More,
Delete and its confirmation. Verify the persisted deletion markers, history,
active attachment list, recoverable bytes and the sibling card's display.

Thanks to AhmedLukman and xet7 !
2026-11-15 20:27:38 +03:00
Ahmed Lukman 7875220470 Soft-delete attachments when removing their card
Find live attachments by their metadata card ID and use the existing
attachment deletion lifecycle. Preserve recoverable bytes and history while
removing the files from active attachment listings.

Cover single and bulk REST deletion, rejected requests, existing soft-deleted
files, history, byte preservation and the remaining card's browser display.

Thanks to AhmedLukman and xet7 !
2026-11-15 20:02:43 +03:00
Ahmed Lukman 628a69c086 Keep renamed upload paths consistent before validation
Update the original and version paths in memory and in the file record, and wait for metadata writes before upload hooks continue. Cover rename failures, persistence ordering, normalized uploads, original bytes and card rendering.
2026-11-15 14:11:10 +03:00
github-actions[bot] ac39a9a6b0 Bump versions for v13.13 2026-11-15 01:36:09 +00:00
Lauri Ojansivu 59d3fc9690 Prepare v13.13 release 2026-11-15 03:35:08 +02:00
Lauri Ojansivu 9e970b87fa Updated ChangeLog.
Thanks to ChrisMagnuson, dependabot and xet7 !
2026-11-15 03:11:44 +02:00
Lauri Ojansivu e46d7a2376 Destination pickers list the cards of a lazily loaded board.
Copy Checklist's card dropdown stayed empty for a board with more cards
than the lazy-loading threshold (CARDS_LOADING=auto above 500, or lazy).
The pickers read the chosen board's cards from the `board` publication,
which ships no cards for a lazy board, and a picker opens no list that
would fetch its window. A new `destinationCards` publication ships the
titles and places of one list's cards in one swimlane (or of the whole
board for the parent-card picker), whatever the card-loading mode, scoped
like the other card publications: the board must be readable, and an
assigned-only member gets only their own cards.

Copy / Move checklist, Copy checklist from a template card, Move / Copy
card, Link card and the parent-card picker subscribe to it. Done waits
until the chosen list's cards are there, a remembered card is checked
against them rather than against the board, and the open board's Filter
no longer empties the destination list.

Thanks to ChrisMagnuson and xet7 !

Fixes #6917.
2026-11-15 03:11:14 +02:00
Lauri Ojansivu c05be372aa Merge pull request #6914 from wekan/dependabot/npm_and_yarn/mongodb-7.8.0
Bump mongodb from 7.7.0 to 7.8.0
2026-11-15 01:48:01 +02:00
dependabot[bot] 7377f88aca Bump mongodb from 7.7.0 to 7.8.0
Bumps [mongodb](https://github.com/mongodb/node-mongodb-native) from 7.7.0 to 7.8.0.
- [Release notes](https://github.com/mongodb/node-mongodb-native/releases)
- [Changelog](https://github.com/mongodb/node-mongodb-native/blob/main/HISTORY.md)
- [Commits](https://github.com/mongodb/node-mongodb-native/compare/v7.7.0...v7.8.0)

---
updated-dependencies:
- dependency-name: mongodb
  dependency-version: 7.8.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-14 23:46:20 +00:00
Lauri Ojansivu 22577312a9 Merge pull request #6916 from wekan/dependabot/npm_and_yarn/sanitize-html-2.18.2
Bump sanitize-html from 2.18.1 to 2.18.2
2026-11-15 01:45:52 +02:00
Lauri Ojansivu b523e4a517 Merge pull request #6915 from wekan/dependabot/npm_and_yarn/i18next-27.1.1
Bump i18next from 26.5.11 to 27.1.1
2026-11-15 01:45:26 +02:00
Lauri Ojansivu 1810796dc6 Merge pull request #6913 from wekan/dependabot/npm_and_yarn/typescript-eslint/parser-8.72.2
Bump @typescript-eslint/parser from 8.72.1 to 8.72.2
2026-11-15 01:44:42 +02:00
Lauri Ojansivu 8cc5567649 Merge pull request #6912 from wekan/dependabot/github_actions/softprops/action-gh-release-3.0.4
Bump softprops/action-gh-release from 3.0.3 to 3.0.4
2026-11-15 01:44:27 +02:00
Lauri Ojansivu 3d96445be8 Merge pull request #6911 from wekan/dependabot/npm_and_yarn/tests/playwright/playwright/test-1.65.0
Bump @playwright/test from 1.64.1 to 1.65.0 in /tests/playwright
2026-11-15 01:44:08 +02:00
Lauri Ojansivu 26578fcc4e Merge pull request #6910 from wekan/dependabot/github_actions/docker/login-action-4.8.0
Bump docker/login-action from 4.7.0 to 4.8.0
2026-11-15 01:43:48 +02:00
Lauri Ojansivu 8cac055c59 Merge pull request #6909 from wekan/dependabot/npm_and_yarn/puppeteer-25.17.0
Bump puppeteer from 25.15.0 to 25.17.0
2026-11-15 01:43:28 +02:00
Lauri Ojansivu 30d6826564 Merge pull request #6908 from wekan/dependabot/github_actions/azure/setup-helm-5.1.0
Bump azure/setup-helm from 5.0.1 to 5.1.0
2026-11-15 01:42:56 +02:00
Lauri Ojansivu b32234cc9c Merge pull request #6907 from wekan/dependabot/github_actions/vmactions/freebsd-vm-1.6.0
Bump vmactions/freebsd-vm from 1.5.9 to 1.6.0
2026-11-15 01:42:27 +02:00
dependabot[bot] 8b213d38c9 Bump sanitize-html from 2.18.1 to 2.18.2
Bumps [sanitize-html](https://github.com/apostrophecms/apostrophe/tree/HEAD/packages/sanitize-html) from 2.18.1 to 2.18.2.
- [Changelog](https://github.com/apostrophecms/apostrophe/blob/sanitize-html@2.18.2/packages/sanitize-html/CHANGELOG.md)
- [Commits](https://github.com/apostrophecms/apostrophe/commits/sanitize-html@2.18.2/packages/sanitize-html)

---
updated-dependencies:
- dependency-name: sanitize-html
  dependency-version: 2.18.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-14 20:33:27 +00:00
dependabot[bot] 74b004333b Bump i18next from 26.5.11 to 27.1.1
Bumps [i18next](https://github.com/i18next/i18next) from 26.5.11 to 27.1.1.
- [Release notes](https://github.com/i18next/i18next/releases)
- [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md)
- [Commits](https://github.com/i18next/i18next/compare/v26.5.11...v27.1.1)

---
updated-dependencies:
- dependency-name: i18next
  dependency-version: 27.1.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-14 20:33:17 +00:00
dependabot[bot] f04beb1622 Bump @typescript-eslint/parser from 8.72.1 to 8.72.2
Bumps [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) from 8.72.1 to 8.72.2.
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.72.2/packages/parser)

---
updated-dependencies:
- dependency-name: "@typescript-eslint/parser"
  dependency-version: 8.72.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-14 20:33:02 +00:00
dependabot[bot] f9b52fbd9d Bump softprops/action-gh-release from 3.0.3 to 3.0.4
Bumps [softprops/action-gh-release](https://github.com/softprops/action-gh-release) from 3.0.3 to 3.0.4.
- [Release notes](https://github.com/softprops/action-gh-release/releases)
- [Changelog](https://github.com/softprops/action-gh-release/blob/master/CHANGELOG.md)
- [Commits](https://github.com/softprops/action-gh-release/compare/efb35369e0ad2afab669f228072c1b0d510eae64...8a0cd651e5b2365bd640854a3fa5dfc70e4875f3)

---
updated-dependencies:
- dependency-name: softprops/action-gh-release
  dependency-version: 3.0.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-14 20:33:00 +00:00
dependabot[bot] 74b1df33d1 Bump @playwright/test from 1.64.1 to 1.65.0 in /tests/playwright
Bumps [@playwright/test](https://github.com/microsoft/playwright) from 1.64.1 to 1.65.0.
- [Release notes](https://github.com/microsoft/playwright/releases)
- [Commits](https://github.com/microsoft/playwright/compare/v1.64.1...v1.65.0)

---
updated-dependencies:
- dependency-name: "@playwright/test"
  dependency-version: 1.65.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-14 20:32:55 +00:00
dependabot[bot] fa8303dbe4 Bump docker/login-action from 4.7.0 to 4.8.0
Bumps [docker/login-action](https://github.com/docker/login-action) from 4.7.0 to 4.8.0.
- [Release notes](https://github.com/docker/login-action/releases)
- [Commits](https://github.com/docker/login-action/compare/81c6f93d4bc991e510b342a00b419b3bb4efc5c6...8aa5831fb8d48d8f76594c7ddde61ae58019f550)

---
updated-dependencies:
- dependency-name: docker/login-action
  dependency-version: 4.8.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-14 20:32:52 +00:00
dependabot[bot] 5346efb843 Bump puppeteer from 25.15.0 to 25.17.0
Bumps [puppeteer](https://github.com/puppeteer/puppeteer) from 25.15.0 to 25.17.0.
- [Release notes](https://github.com/puppeteer/puppeteer/releases)
- [Changelog](https://github.com/puppeteer/puppeteer/blob/main/CHANGELOG.md)
- [Commits](https://github.com/puppeteer/puppeteer/compare/puppeteer-v25.15.0...puppeteer-v25.17.0)

---
updated-dependencies:
- dependency-name: puppeteer
  dependency-version: 25.17.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-14 20:32:49 +00:00
dependabot[bot] 164809e08b Bump azure/setup-helm from 5.0.1 to 5.1.0
Bumps [azure/setup-helm](https://github.com/azure/setup-helm) from 5.0.1 to 5.1.0.
- [Release notes](https://github.com/azure/setup-helm/releases)
- [Changelog](https://github.com/Azure/setup-helm/blob/main/CHANGELOG.md)
- [Commits](https://github.com/azure/setup-helm/compare/9bc31f4ebc9c6b171d7bfbaa5d006ae7abdb4310...2f5e7bc67f1f9972ab16657bb795f36d8f04de0e)

---
updated-dependencies:
- dependency-name: azure/setup-helm
  dependency-version: 5.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-14 20:32:45 +00:00
dependabot[bot] ae6ee35bdb Bump vmactions/freebsd-vm from 1.5.9 to 1.6.0
Bumps [vmactions/freebsd-vm](https://github.com/vmactions/freebsd-vm) from 1.5.9 to 1.6.0.
- [Release notes](https://github.com/vmactions/freebsd-vm/releases)
- [Commits](https://github.com/vmactions/freebsd-vm/compare/c46abacb49f09938ca4e1702d15d836285d694cc...811efaaac0668df8bfb8308c3ec997b5ab50037b)

---
updated-dependencies:
- dependency-name: vmactions/freebsd-vm
  dependency-version: 1.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-14 20:32:39 +00:00
574 changed files with 18923 additions and 2669 deletions

No files matched your search

+2 -2
View File
@@ -149,8 +149,8 @@ jobs:
esac
docker run --rm --security-opt seccomp=unconfined -v "$PWD:/work" -w /work \
"termux/termux-docker:$TERMUX_ARCH" env "ARCH=$ARCH" DO_NOT_TRACK=1 bash -ec '
apt-get update
apt-get install -y nodejs-lts python make clang pkg-config libvips curl procps file
APT_ATTEMPTS=5 APT_SLEEPS="30 60 120 180" bash releases/apt-install.sh \
nodejs-lts python make clang pkg-config libvips curl procps file
bash releases/android/build-bundle.sh "$ARCH"'
- name: Package
+28 -5
View File
@@ -147,13 +147,21 @@ jobs:
- name: Build and start in FreeBSD
if: steps.node.outputs.skip != 'true' && matrix.os == 'freebsd'
uses: vmactions/freebsd-vm@c46abacb49f09938ca4e1702d15d836285d694cc
uses: vmactions/freebsd-vm@811efaaac0668df8bfb8308c3ec997b5ab50037b
with:
release: ${{ matrix.release }}
arch: ${{ matrix.vm_arch }}
sync: rsync
copyback: true
prepare: pkg install -y bash python3 gmake pkgconf curl
prepare: |
# A package mirror that is briefly unreachable ("No route to host",
# v13.18) is waited out instead of failing the build.
for i in 1 2 3 4 5; do
pkg install -y bash python3 gmake pkgconf curl && break
[ "$i" = 5 ] && { echo "::error::Installing the VM's packages failed 5 times: the package mirror is down, not WeKan. Re-run this job."; exit 1; }
echo "Package install failed (attempt $i/5), retrying."
sleep $((i * 30))
done
run: bash releases/bsd/build-bundle.sh freebsd ${{ matrix.arch }}
- name: Build and start in OpenBSD
@@ -164,7 +172,15 @@ jobs:
arch: ${{ matrix.vm_arch }}
sync: rsync
copyback: true
prepare: pkg_add bash python%3 gmake curl
prepare: |
# A package mirror that is briefly unreachable ("No route to host",
# v13.18) is waited out instead of failing the build.
for i in 1 2 3 4 5; do
pkg_add bash python%3 gmake curl && break
[ "$i" = 5 ] && { echo "::error::Installing the VM's packages failed 5 times: the package mirror is down, not WeKan. Re-run this job."; exit 1; }
echo "Package install failed (attempt $i/5), retrying."
sleep $((i * 30))
done
# V8 writes and runs machine code: OpenBSD allows that only from a
# filesystem mounted wxallowed (/usr/local is, by default). The
# bundle is started here, from the workspace, so that is mounted so.
@@ -180,8 +196,15 @@ jobs:
sync: rsync
copyback: true
prepare: |
/usr/sbin/pkg_add pkgin
pkgin -y install bash python313 gmake curl gcc14
# A package mirror that is briefly unreachable ("No route to host",
# v13.18) is waited out instead of failing the build.
for i in 1 2 3 4 5; do
{ command -v pkgin >/dev/null || /usr/sbin/pkg_add pkgin; } &&
pkgin -y install bash python313 gmake curl gcc14 && break
[ "$i" = 5 ] && { echo "::error::Installing the VM's packages failed 5 times: the package mirror is down, not WeKan. Re-run this job."; exit 1; }
echo "Package install failed (attempt $i/5), retrying."
sleep $((i * 30))
done
# Node 26's headers need C++20, which NetBSD 10's own GCC lacks: the
# native modules are compiled with pkgsrc's GCC 14, as Node.js itself
# is (wekan/node-patches dist/netbsd).
+15 -4
View File
@@ -232,12 +232,15 @@ jobs:
"TARGET=$TARGET" "TARGET_PLATFORM=$TARGET_PLATFORM" \
"TARGET_ARCH=$TARGET_ARCH" "RELEASE_TAG=$RELEASE_TAG" \
DO_NOT_TRACK=1 bash -ec '
apt-get update
apt-get install -y nodejs-lts python make clang pkg-config libvips
# A Termux mirror mid-sync fails the index ("File has unexpected
# size ... Mirror sync in progress?", v13.18): apt-install.sh waits
# it out.
APT_ATTEMPTS=5 APT_SLEEPS="30 60 120 180" bash releases/apt-install.sh \
nodejs-lts python make clang pkg-config libvips
bash releases/bun/build-target.sh'
- name: FreeBSD VM build and smoke tests
if: matrix.kind == 'freebsd'
uses: vmactions/freebsd-vm@c46abacb49f09938ca4e1702d15d836285d694cc # v1.5.9
uses: vmactions/freebsd-vm@811efaaac0668df8bfb8308c3ec997b5ab50037b # v1.6.0
with:
release: '14.5'
arch: ${{ matrix.vm_arch }}
@@ -245,7 +248,15 @@ jobs:
sync: rsync
copyback: true
cache-after-prepare: true
prepare: pkg install -y bash node24 npm-node24 python3 gmake pkgconf vips
prepare: |
# A package mirror that is briefly unreachable ("No route to host",
# v13.18) is waited out instead of failing the build.
for i in 1 2 3 4 5; do
pkg install -y bash node24 npm-node24 python3 gmake pkgconf vips && break
[ "$i" = 5 ] && { echo "::error::Installing the VM's packages failed 5 times: the package mirror is down, not WeKan. Re-run this job."; exit 1; }
echo "Package install failed (attempt $i/5), retrying."
sleep $((i * 30))
done
run: bash releases/bun/build-target.sh
- name: Check finished archive exists
id: ready
+1 -1
View File
@@ -72,7 +72,7 @@ jobs:
# https://github.com/docker/login-action
- name: Log into registry ${{ env.REGISTRY }}
if: github.event_name != 'pull_request'
uses: docker/login-action@81c6f93d4bc991e510b342a00b419b3bb4efc5c6
uses: docker/login-action@8aa5831fb8d48d8f76594c7ddde61ae58019f550
with:
registry: ${{ env.REGISTRY }}
username: ${{ github.actor }}
+1 -1
View File
@@ -486,7 +486,7 @@ jobs:
- name: Install Helm
if: steps.check.outputs.skip != 'true'
uses: azure/setup-helm@9bc31f4ebc9c6b171d7bfbaa5d006ae7abdb4310 # v5.0.1
uses: azure/setup-helm@2f5e7bc67f1f9972ab16657bb795f36d8f04de0e # v5.1.0
- name: Publish the chart for this release
if: steps.check.outputs.skip != 'true'
+2 -2
View File
@@ -538,7 +538,7 @@ jobs:
path: charts
- name: Install Helm
uses: azure/setup-helm@9bc31f4ebc9c6b171d7bfbaa5d006ae7abdb4310 # v5.0.1
uses: azure/setup-helm@2f5e7bc67f1f9972ab16657bb795f36d8f04de0e # v5.1.0
- name: Fetch gh-pages branch (release-charts.sh switches to it)
run: |
@@ -1220,7 +1220,7 @@ jobs:
# loudly and verified from the release side; the next step checks the two
# base bundles from here.
- name: Create GitHub Release
uses: softprops/action-gh-release@efb35369e0ad2afab669f228072c1b0d510eae64 # v3.0.3
uses: softprops/action-gh-release@8a0cd651e5b2365bd640854a3fa5dfc70e4875f3 # v3.0.4
with:
tag_name: v${{ needs.prepare.outputs.version }}
name: v${{ needs.prepare.outputs.version }}
+1 -2
View File
@@ -185,8 +185,7 @@ jobs:
esac
chmod +x host32/node
sudo dpkg --add-architecture i386
sudo apt-get update -qq
sudo apt-get install -y -qq libc6:i386 libstdc++6:i386 libatomic1:i386 >/dev/null
bash releases/apt-install.sh libc6:i386 libstdc++6:i386 libatomic1:i386
host="$PWD/host32/node"
got="$("$host" -p process.version)"
[ "$got" = "$NODE_VERSION" ] || { echo "::error::The i386 Node.js resolved for $NODE_VERSION reports $got."; exit 1; }
+60 -40
View File
@@ -166,7 +166,7 @@ git config user.name && git config user.email
declined without holding up the others.
- **No changelog changes.** Do not edit `CHANGELOG-big.md`, `CHANGELOG.md`, or the
`CHANGELOG.md` or `CHANGELOG` of a repository under `.tools/` — not an Upcoming
entry, not TODO Later. Describe the change in the pull request instead. The
entry, and not `TODO.md` either. Describe the change in the pull request instead. The
maintainer writes the entry after merging, when there is a commit for it to link.
Who that pull request credits follows the attribution rule above, and the two
@@ -267,6 +267,32 @@ replaced with the language named by that tag.**
misrepresent machine/LLM translations as human. Push only separately reviewed,
provenance-known human translations with an explicit push command.
### Shared translation source for WeKan prototypes under `.tools/`
The WeKan catalogs in `imports/i18n/data/` are the source of truth for
translations in every WeKan prototype under `.tools/`, including WeLite,
Weddy, Wami, and any future WeKan prototype with its own catalog.
1. Before adding a translation key in a prototype, search WeKan's English
catalog for a key with the same meaning and usage. Reuse that key and its
existing translations. A different key name or catalog format does not
require a new translation.
2. If no suitable key exists, add it to WeKan's English catalog first, even if
the string is currently used only by a prototype. Fill the key for every
supported language in the WeKan repository using the translation rules
below. Preserve existing human translations and verify the placeholders
against the English source.
3. Once the key is complete in WeKan, copy the canonical translations into
the applicable WeKan prototype repositories under `.tools/`. Use each
prototype's catalog format, filename and locale mapping as needed, while
preserving the translated text and placeholders. Verify that the prototype
loads the synced catalogs and renders the intended strings.
Apply the same workflow to existing prototype-only keys and translation
corrections. Resolve equivalent keys and bring genuinely new strings into
WeKan before syncing them back out. Maintain translation text in WeKan so the
prototypes share the same translations and receive subsequent updates.
### Filling the remaining untranslated strings — directly, no translation service
The strings still equal to the English source after the merge are the ones untranslated
@@ -440,7 +466,7 @@ directly after the merge.
| Repository | File | Format |
| --- | --- | --- |
| `wekan/wekan` | `CHANGELOG-big.md` (and the generated `CHANGELOG.md`, below) | the WeKan format this section describes: `# Status` (Platforms/Version/TODO Later nested as `<details>`), then `# v<MAJOR>.<MINOR> YYYY-MM-DD WeKan ® release` sections of `<details>` entries whose `<summary>` links the commit |
| `wekan/wekan` | `CHANGELOG-big.md` (and the generated `CHANGELOG.md`, below) | the WeKan format this section describes: `# Status` (Platforms/Version nested as `<details>`), then `# v<MAJOR>.<MINOR> YYYY-MM-DD WeKan ® release` sections of `<details>` entries whose `<summary>` links the commit |
| `wekan/node-patches` | `CHANGELOG.md` | the same WeKan format, with `# Upcoming node-patches release` |
| `wekan/mongo-tools-patches` | `CHANGELOG.md` | the same WeKan format, with `# Upcoming mongo-tools-patches release` |
| `wekan/FerretDB` | `CHANGELOG.md` | **upstream FerretDB's** format, not WeKan's: `## [v1.48.0](tag URL) (YYYY-MM-DD)` and `### New Features 🎉` / `### Fixed 🐛` / `### Other Changes 🤖` bullets ending `by @xet7. Thanks to xet7.` |
@@ -461,7 +487,7 @@ directly after the merge.
| | `CHANGELOG.md` |
| --- | --- |
| Status, TODO Later | none |
| Status | none |
| First | the unreleased `# Upcoming WeKan ® release`, when there is one: its **In short** paragraph only, then `[All changes so far](CHANGELOG-big.md#upcoming-wekan--release)` |
| Below it | the five newest `# v<MAJOR>.<MINOR> YYYY-MM-DD WeKan ® release` |
| Per release | its **In short** paragraph only, then `[All changes in v…](CHANGELOG-big.md#anchor)` |
@@ -521,7 +547,7 @@ directly after the merge.
| | |
| --- | --- |
| `CHANGELOG-big.md` | `# Status` (Platforms/TODO Later inside it), `# Upcoming`, and the newest releases that fit the budget |
| `CHANGELOG-big.md` | `# Status` (Platforms/Version inside it), `# Upcoming`, and the newest releases that fit the budget |
| `old-CHANGELOG/<year>/<MM>.md` | a month's releases, newest first; a month over the budget continues in `<MM>-part2.md`, `<MM>-part3.md`, ... |
| `old-CHANGELOG/<year>.md` | 2015–2025, whole |
@@ -544,24 +570,22 @@ directly after the merge.
An archived section is never edited, for the same reason a released one is
not.
- **The file's shape, top to bottom** — keep it exactly as it is now. There is
exactly ONE `#` heading before the releases: `# Status`. Platforms, Version
and TODO Later are `<details>` blocks nested inside it, not headings of
their own (they used to be `# Platforms` and `# TODO Later`; both were
folded under `# Status` so the file opens with a single top-level section
rather than three):
exactly ONE `#` heading before the releases: `# Status`. Platforms and Version
are `<details>` blocks nested inside it, not headings of their own (they used
to be `# Platforms` and `# TODO Later`; Platforms was folded under `# Status`
so the file opens with a single top-level section, and TODO Later moved out
to `TODO.md`, below):
1. `# Status` — opens with a `<details>` whose `<summary>` is `More status
info`, holding a link to <https://wekan.fi/status/>. Then a `<details>`
info`, holding a link to <https://wekan.fi/status/> and the line pointing
to [TODO.md](TODO.md). Then a `<details>`
whose `<summary>` is `Newest WeKan at these platforms`, holding the line
`Newest WeKan at these platforms:` and the Install / Upgrade / Docs / Mac
ChangeLog bullets, plus the `Older releases:` bullet linking the per-year
archives. Then a `<details>` whose `<summary>` is `Databases` listing
which databases WeKan supports and how each is tested, kept in step with
`docs/Databases/Supported.md`. Then a `<details>` whose `<summary>` is `Version` holding
"which WeKan version uses what". Then a `<details>` whose `<summary>` is
`TODO Later`, itself holding a `<details>` whose `<summary>` is `Carried
to a future release.` explaining the list, then one `<details>` per
category (below). There is no `# Version` or `# TODO Later` heading of
its own.
"which WeKan version uses what". There is no `# Version` heading of its
own, and no TODO Later block: what is not done is in `TODO.md`.
2. The releases, newest first, each `# v<MAJOR>.<MINOR> YYYY-MM-DD WeKan ® release`.
Nothing else is an `#` heading. A `##`/`###` inside a release would break the
@@ -605,10 +629,6 @@ directly after the merge.
A `<details>` whose body only
repeats its summary is noise; use one when there IS a longer story to reveal, which
is most fixes.
- **TODO Later's own blocks are the same shape with two differences:** the `<summary>` is
the short category text (no `<a>`, because nothing was committed), and there is **no
`Thanks to`** — nothing is done yet, so there is nobody to thank. The body lists the
issues as `[#NNNN](https://github.com/wekan/wekan/issues/NNNN) (one-line reason)`.
- **The hash is never the link text.** `[f1c89548e](…)` shows a hash to a reader who
cannot do anything with it; the link text says what changed. Same for `[merge
commit](…)` and for a bare URL — see the next rule.
@@ -707,27 +727,27 @@ directly after the merge.
`This release fixes the following SECURITY ISSUES found by GitHub CodeQL code scanning:`.
Because CRITICAL comes first, it keeps the `This release ` prefix; a following non-security
subsection becomes `and …` per the rule above.
- **TODO Later** — a `<details>` nested inside `# Status` near the TOP of
`CHANGELOG-big.md` (above the version sections), a triage backlog for open
issues that were **investigated but not fixed here**, each
recorded with a concrete REASON so whoever picks it up next knows why. Use it when working
through open issues (the "Fix open issues" process): for each issue, either **fix it** (commit
ending `Fixes #NNNN,`), **close it** if already fixed in current code (commit `Close #NNNN` /
`Fixes #NNNN,`), or — when it can't be fixed/verified in this environment — **add it to `TODO
Later` under the matching category with the reason**. Group issues by category bullet, e.g.:
*Need specific infrastructure / a running server stack* (LDAP/WebHooks/Sandstorm/proxy —
environment owners), *Need the running app to reproduce/verify* (runtime UI / publication /
mergebox / router state, not unit-testable), *Already correct in the current code* (verified by
reading; could not reproduce), *Feature requests / behaviour-by-design rather than bugs*, and
*Needs a maintainer decision on the intended contract*. Each category is a `<details>`
whose `<summary>` is the SHORT category text and whose body lists the issues with their
reasons — and with **no `Thanks to` line**, because nothing is done yet, so there is
nobody to thank. Each entry is a normal issue link
`[#NNNN](https://github.com/wekan/wekan/issues/NNNN) (one-line reason)` — issue links here, NOT
commit links (nothing was committed). **Keep it current:** when an issue in `TODO Later` gets
fixed, REMOVE it from the list (its fix commit's `Fixes #NNNN` closes it); do not leave fixed
issues in the backlog. This is the only CHANGELOG place that uses issue links and lives above
the releases; everything else uses the per-release commit-link bullets above.
- **`TODO.md`** — at the repository root, NOT in the changelog (it was the TODO
Later block inside `# Status` until 2026-11-18, when it moved out so the
changelog says only what changed). A triage backlog of work and open issues
that were **investigated but not done here**, each recorded with a concrete
REASON so whoever picks it up next knows why. Use it when working through open
issues (the "Fix open issues" process): for each issue, either **fix it**
(commit ending `Fixes #NNNN,`), **close it** if already fixed in current code
(commit `Close #NNNN` / `Fixes #NNNN,`), or — when it can't be fixed/verified
in this environment — **add it to `TODO.md` under the matching category with
the reason**. Categories are `##` headings there, e.g. *Need specific
infrastructure / a running server stack*, *Need the running app to
reproduce/verify*, *Already correct in the current code*, *Feature requests /
behaviour-by-design rather than bugs* and *Needs a maintainer decision on the
intended contract*; an emptied category is removed. Each entry is a bullet with
a normal issue link `[#NNNN](https://github.com/wekan/wekan/issues/NNNN) (one-line
reason)` when there is an issue — never a commit link, and **no `Thanks to`**,
because nothing is done yet, so there is nobody to thank. **When an item is
done, MOVE it:** remove it from `TODO.md` and write its entry in `# Upcoming
WeKan ® release` of `CHANGELOG-big.md`, linking the commit (its `Fixes #NNNN`
closes the issue). A done item never stays in `TODO.md`.
`tests/todoFile.test.cjs` checks the file.
- FerretDB Upcoming structure — `### New Features 🎉`, `### Fixed 🐛`, `### Other Changes
🤖`; entries end `... by @xet7. Thanks to xet7.`
- Word-wrap both CHANGELOGs at 80 chars, but never break a long link across lines (a
+674 -773
View File
File diff suppressed because it is too large. Load diff
+34 -33
View File
@@ -5,50 +5,51 @@ each one changed and the project status are in
Written by `node releases/changelog-short.mjs` from CHANGELOG-big.md:
make changes there.
# v13.12 2026-11-14 WeKan ® release
# v13.19 2026-11-19 WeKan ® release
WeKan is updated to **Meteor 3.6.1**, whose DDP server refuses
malformed messages without stalling the connection. **One shared list header
row** now shows the same lists in every swimlane, scrolling together, and
**Shift+M** and **Shift+C** open Move Card and Copy Card. Those popups
remember the swimlane and list, not only the board. The embedded-engine
benchmark takes **OpenTelemetry 1.47.0** for a Dependabot alert. A **REST
API** write that changes nothing answers 404, and a card deletion naming the
wrong list no longer strips the card's checklists (**ListLockBleed**).
**Release builds** no longer fail when the **Snap Store** is slow
to process an upload, or when a **Termux** or **BSD** package mirror has a bad
minute.
[All changes in v13.12](CHANGELOG-big.md#v1312-2026-11-14-wekan--release)
[All changes in v13.19](CHANGELOG-big.md#v1319-2026-11-19-wekan--release)
# v13.11 2026-11-13 WeKan ® release
# v13.18 2026-11-19 WeKan ® release
The **file-integrity scan** stops reporting attachments and
avatars that WeKan deleted itself as missing, which had buried real
**StorageBleed** findings under thousands of false ones. The recurring-checklist
reset no longer scans every **checklist** on each tick. In the **REST API**, a
refused custom-field update changes nothing, ownership transfer takes only the
boards the user administers, and deleting a missing integration answers 404.
**Admin Panel / Problems** says what its numbers count - "New
problems: 1" and "Checks with findings: 8 / 31", in every language - and a
report row's address, location and user always belong to the same occurrence.
[All changes in v13.11](CHANGELOG-big.md#v1311-2026-11-13-wekan--release)
[All changes in v13.18](CHANGELOG-big.md#v1318-2026-11-19-wekan--release)
# v13.10 2026-11-13 WeKan ® release
# v13.17 2026-11-19 WeKan ® release
The release's **Snap Store** credential check bounds each
snapcraft install attempt, so a Snap Store that hangs no longer stops a release.
The **Admin Panel** answers one question per tab: Settings gains
**Appearance**, **Features**, **Feature profiles**, Security, Activities and
notifications, and Delete, Problems keeps only what is going wrong, and every
old
address redirects. The docs now have a page for every menu entry, and cards of
an archived swimlane no longer appear in the first swimlane.
[All changes in v13.10](CHANGELOG-big.md#v1310-2026-11-13-wekan--release)
[All changes in v13.17](CHANGELOG-big.md#v1317-2026-11-19-wekan--release)
# v13.09 2026-11-12 WeKan ® release
# v13.16 2026-11-19 WeKan ® release
The release's **Snap Store** credential check retries installing
snapcraft, so one Snap Store timeout no longer stops a release.
**ListLockBulkBleed** is fixed, and a list that refuses a role
now also refuses that role's bulk writes, dependency lines, rule actions and
changes to the list or swimlane itself. Administrators can give chosen users,
teams and organizations a smaller WeKan with opt-in **feature profiles**. A
server no longer runs out of memory in the hourly **History integrity audit**,
**scheduled rules** can create cards again, and **Card Excel export** and
clearing a card's text work again.
[All changes in v13.09](CHANGELOG-big.md#v1309-2026-11-12-wekan--release)
[All changes in v13.16](CHANGELOG-big.md#v1316-2026-11-19-wekan--release)
# v13.08 2026-11-12 WeKan ® release
# v13.15 2026-11-18 WeKan ® release
The **REST API** creates a card under the **parent** it is given,
and a refused **integration URL** no longer leaves the other fields of the same
update written. The **single-file** WeKan for **32-bit ARM** builds again, with
an i386 Node.js of the exact version its bundle embeds. A **GitHub CodeQL**
alert in the security alert download script is fixed.
**RaceBleed** is fixed: deleting a card while somebody moves it
to another board no longer destroys its checklists, comments and attachments
while the card itself survives there, and a member deleting a card that was
just moved keeps their account. REST handlers now answer **404, not 500**, for
a swimlane, user or board that is not there.
[All changes in v13.08](CHANGELOG-big.md#v1308-2026-11-12-wekan--release)
[All changes in v13.15](CHANGELOG-big.md#v1315-2026-11-18-wekan--release)
+60 -40
View File
@@ -166,7 +166,7 @@ git config user.name && git config user.email
declined without holding up the others.
- **No changelog changes.** Do not edit `CHANGELOG-big.md`, `CHANGELOG.md`, or the
`CHANGELOG.md` or `CHANGELOG` of a repository under `.tools/` — not an Upcoming
entry, not TODO Later. Describe the change in the pull request instead. The
entry, and not `TODO.md` either. Describe the change in the pull request instead. The
maintainer writes the entry after merging, when there is a commit for it to link.
Who that pull request credits follows the attribution rule above, and the two
@@ -267,6 +267,32 @@ replaced with the language named by that tag.**
misrepresent machine/LLM translations as human. Push only separately reviewed,
provenance-known human translations with an explicit push command.
### Shared translation source for WeKan prototypes under `.tools/`
The WeKan catalogs in `imports/i18n/data/` are the source of truth for
translations in every WeKan prototype under `.tools/`, including WeLite,
Weddy, Wami, and any future WeKan prototype with its own catalog.
1. Before adding a translation key in a prototype, search WeKan's English
catalog for a key with the same meaning and usage. Reuse that key and its
existing translations. A different key name or catalog format does not
require a new translation.
2. If no suitable key exists, add it to WeKan's English catalog first, even if
the string is currently used only by a prototype. Fill the key for every
supported language in the WeKan repository using the translation rules
below. Preserve existing human translations and verify the placeholders
against the English source.
3. Once the key is complete in WeKan, copy the canonical translations into
the applicable WeKan prototype repositories under `.tools/`. Use each
prototype's catalog format, filename and locale mapping as needed, while
preserving the translated text and placeholders. Verify that the prototype
loads the synced catalogs and renders the intended strings.
Apply the same workflow to existing prototype-only keys and translation
corrections. Resolve equivalent keys and bring genuinely new strings into
WeKan before syncing them back out. Maintain translation text in WeKan so the
prototypes share the same translations and receive subsequent updates.
### Filling the remaining untranslated strings — directly, no translation service
The strings still equal to the English source after the merge are the ones untranslated
@@ -440,7 +466,7 @@ directly after the merge.
| Repository | File | Format |
| --- | --- | --- |
| `wekan/wekan` | `CHANGELOG-big.md` (and the generated `CHANGELOG.md`, below) | the WeKan format this section describes: `# Status` (Platforms/Version/TODO Later nested as `<details>`), then `# v<MAJOR>.<MINOR> YYYY-MM-DD WeKan ® release` sections of `<details>` entries whose `<summary>` links the commit |
| `wekan/wekan` | `CHANGELOG-big.md` (and the generated `CHANGELOG.md`, below) | the WeKan format this section describes: `# Status` (Platforms/Version nested as `<details>`), then `# v<MAJOR>.<MINOR> YYYY-MM-DD WeKan ® release` sections of `<details>` entries whose `<summary>` links the commit |
| `wekan/node-patches` | `CHANGELOG.md` | the same WeKan format, with `# Upcoming node-patches release` |
| `wekan/mongo-tools-patches` | `CHANGELOG.md` | the same WeKan format, with `# Upcoming mongo-tools-patches release` |
| `wekan/FerretDB` | `CHANGELOG.md` | **upstream FerretDB's** format, not WeKan's: `## [v1.48.0](tag URL) (YYYY-MM-DD)` and `### New Features 🎉` / `### Fixed 🐛` / `### Other Changes 🤖` bullets ending `by @xet7. Thanks to xet7.` |
@@ -461,7 +487,7 @@ directly after the merge.
| | `CHANGELOG.md` |
| --- | --- |
| Status, TODO Later | none |
| Status | none |
| First | the unreleased `# Upcoming WeKan ® release`, when there is one: its **In short** paragraph only, then `[All changes so far](CHANGELOG-big.md#upcoming-wekan--release)` |
| Below it | the five newest `# v<MAJOR>.<MINOR> YYYY-MM-DD WeKan ® release` |
| Per release | its **In short** paragraph only, then `[All changes in v…](CHANGELOG-big.md#anchor)` |
@@ -521,7 +547,7 @@ directly after the merge.
| | |
| --- | --- |
| `CHANGELOG-big.md` | `# Status` (Platforms/TODO Later inside it), `# Upcoming`, and the newest releases that fit the budget |
| `CHANGELOG-big.md` | `# Status` (Platforms/Version inside it), `# Upcoming`, and the newest releases that fit the budget |
| `old-CHANGELOG/<year>/<MM>.md` | a month's releases, newest first; a month over the budget continues in `<MM>-part2.md`, `<MM>-part3.md`, ... |
| `old-CHANGELOG/<year>.md` | 2015–2025, whole |
@@ -544,24 +570,22 @@ directly after the merge.
An archived section is never edited, for the same reason a released one is
not.
- **The file's shape, top to bottom** — keep it exactly as it is now. There is
exactly ONE `#` heading before the releases: `# Status`. Platforms, Version
and TODO Later are `<details>` blocks nested inside it, not headings of
their own (they used to be `# Platforms` and `# TODO Later`; both were
folded under `# Status` so the file opens with a single top-level section
rather than three):
exactly ONE `#` heading before the releases: `# Status`. Platforms and Version
are `<details>` blocks nested inside it, not headings of their own (they used
to be `# Platforms` and `# TODO Later`; Platforms was folded under `# Status`
so the file opens with a single top-level section, and TODO Later moved out
to `TODO.md`, below):
1. `# Status` — opens with a `<details>` whose `<summary>` is `More status
info`, holding a link to <https://wekan.fi/status/>. Then a `<details>`
info`, holding a link to <https://wekan.fi/status/> and the line pointing
to [TODO.md](TODO.md). Then a `<details>`
whose `<summary>` is `Newest WeKan at these platforms`, holding the line
`Newest WeKan at these platforms:` and the Install / Upgrade / Docs / Mac
ChangeLog bullets, plus the `Older releases:` bullet linking the per-year
archives. Then a `<details>` whose `<summary>` is `Databases` listing
which databases WeKan supports and how each is tested, kept in step with
`docs/Databases/Supported.md`. Then a `<details>` whose `<summary>` is `Version` holding
"which WeKan version uses what". Then a `<details>` whose `<summary>` is
`TODO Later`, itself holding a `<details>` whose `<summary>` is `Carried
to a future release.` explaining the list, then one `<details>` per
category (below). There is no `# Version` or `# TODO Later` heading of
its own.
"which WeKan version uses what". There is no `# Version` heading of its
own, and no TODO Later block: what is not done is in `TODO.md`.
2. The releases, newest first, each `# v<MAJOR>.<MINOR> YYYY-MM-DD WeKan ® release`.
Nothing else is an `#` heading. A `##`/`###` inside a release would break the
@@ -605,10 +629,6 @@ directly after the merge.
A `<details>` whose body only
repeats its summary is noise; use one when there IS a longer story to reveal, which
is most fixes.
- **TODO Later's own blocks are the same shape with two differences:** the `<summary>` is
the short category text (no `<a>`, because nothing was committed), and there is **no
`Thanks to`** — nothing is done yet, so there is nobody to thank. The body lists the
issues as `[#NNNN](https://github.com/wekan/wekan/issues/NNNN) (one-line reason)`.
- **The hash is never the link text.** `[f1c89548e](…)` shows a hash to a reader who
cannot do anything with it; the link text says what changed. Same for `[merge
commit](…)` and for a bare URL — see the next rule.
@@ -707,27 +727,27 @@ directly after the merge.
`This release fixes the following SECURITY ISSUES found by GitHub CodeQL code scanning:`.
Because CRITICAL comes first, it keeps the `This release ` prefix; a following non-security
subsection becomes `and …` per the rule above.
- **TODO Later** — a `<details>` nested inside `# Status` near the TOP of
`CHANGELOG-big.md` (above the version sections), a triage backlog for open
issues that were **investigated but not fixed here**, each
recorded with a concrete REASON so whoever picks it up next knows why. Use it when working
through open issues (the "Fix open issues" process): for each issue, either **fix it** (commit
ending `Fixes #NNNN,`), **close it** if already fixed in current code (commit `Close #NNNN` /
`Fixes #NNNN,`), or — when it can't be fixed/verified in this environment — **add it to `TODO
Later` under the matching category with the reason**. Group issues by category bullet, e.g.:
*Need specific infrastructure / a running server stack* (LDAP/WebHooks/Sandstorm/proxy —
environment owners), *Need the running app to reproduce/verify* (runtime UI / publication /
mergebox / router state, not unit-testable), *Already correct in the current code* (verified by
reading; could not reproduce), *Feature requests / behaviour-by-design rather than bugs*, and
*Needs a maintainer decision on the intended contract*. Each category is a `<details>`
whose `<summary>` is the SHORT category text and whose body lists the issues with their
reasons — and with **no `Thanks to` line**, because nothing is done yet, so there is
nobody to thank. Each entry is a normal issue link
`[#NNNN](https://github.com/wekan/wekan/issues/NNNN) (one-line reason)` — issue links here, NOT
commit links (nothing was committed). **Keep it current:** when an issue in `TODO Later` gets
fixed, REMOVE it from the list (its fix commit's `Fixes #NNNN` closes it); do not leave fixed
issues in the backlog. This is the only CHANGELOG place that uses issue links and lives above
the releases; everything else uses the per-release commit-link bullets above.
- **`TODO.md`** — at the repository root, NOT in the changelog (it was the TODO
Later block inside `# Status` until 2026-11-18, when it moved out so the
changelog says only what changed). A triage backlog of work and open issues
that were **investigated but not done here**, each recorded with a concrete
REASON so whoever picks it up next knows why. Use it when working through open
issues (the "Fix open issues" process): for each issue, either **fix it**
(commit ending `Fixes #NNNN,`), **close it** if already fixed in current code
(commit `Close #NNNN` / `Fixes #NNNN,`), or — when it can't be fixed/verified
in this environment — **add it to `TODO.md` under the matching category with
the reason**. Categories are `##` headings there, e.g. *Need specific
infrastructure / a running server stack*, *Need the running app to
reproduce/verify*, *Already correct in the current code*, *Feature requests /
behaviour-by-design rather than bugs* and *Needs a maintainer decision on the
intended contract*; an emptied category is removed. Each entry is a bullet with
a normal issue link `[#NNNN](https://github.com/wekan/wekan/issues/NNNN) (one-line
reason)` when there is an issue — never a commit link, and **no `Thanks to`**,
because nothing is done yet, so there is nobody to thank. **When an item is
done, MOVE it:** remove it from `TODO.md` and write its entry in `# Upcoming
WeKan ® release` of `CHANGELOG-big.md`, linking the commit (its `Fixes #NNNN`
closes the issue). A done item never stays in `TODO.md`.
`tests/todoFile.test.cjs` checks the file.
- FerretDB Upcoming structure — `### New Features 🎉`, `### Fixed 🐛`, `### Other Changes
🤖`; entries end `... by @xet7. Thanks to xet7.`
- Word-wrap both CHANGELOGs at 80 chars, but never break a long link across lines (a
+2 -2
View File
@@ -38,7 +38,7 @@ FROM --platform=$BUILDPLATFORM debian:trixie AS bundle
ARG TARGETARCH
ARG TARGETVARIANT
ARG VERSION=13.12
ARG VERSION=13.19
ARG DEBIAN_FRONTEND=noninteractive
COPY --chmod=755 releases/check-telemetry.py /tmp/check-telemetry.py
@@ -151,7 +151,7 @@ ENV \
NODE_VERSION=v26.13.1 \
METEOR_RELEASE=METEOR@3.6.1 \
USE_EDGE=false \
NPM_VERSION=12.2.2 \
NPM_VERSION=12.2.3 \
SRC_PATH=./ \
WITH_API=true \
MONGO_OPLOG_URL="" \
+1 -1
View File
@@ -1,5 +1,5 @@
appId: wekan-public/apps/77b94f60-dec9-0136-304e-16ff53095928
appVersion: "v13.12.0"
appVersion: "v13.19.0"
files:
userUploads:
- README.md
+47
View File
@@ -0,0 +1,47 @@
# TODO
What is not done yet in WeKan, with the reason it is not done. This used to be
the TODO Later block inside `# Status` of `CHANGELOG-big.md`; it lives here so
the changelog only says what changed.
- An item here is NOT done, so it thanks nobody and links no commit. Link the
issue when there is one: `[#NNNN](https://github.com/wekan/wekan/issues/NNNN)`
and a one-line reason.
- When an item is done, REMOVE it from this file and write its entry in the
`# Upcoming WeKan ® release` section of `CHANGELOG-big.md`, linking the commit.
A fixed item never stays here.
- An investigated issue that cannot be fixed or verified here is added under
the category that says why. An emptied category is removed.
`tests/todoFile.test.cjs` checks this shape.
## Need the running app to reproduce/verify
- The WebKit stage cannot run in the Flatpak sandbox: MiniBrowser needs its own
sandbox, and turning that off is not allowed there. Run it on a host.
## Found while documenting the menus, to fix
- Member menu / Edit Profile: with Admin Panel / People / Login **Username
change** allowed, a user's new username is not saved - `setUsername`
(`server/models/users.js`) writes only when the caller is a site admin, while
`setEmail` beside it allows a self change when the setting says so. The popup
closes as if it had saved. Found on 2026-11-19.
- Member menu / Support: the Support page template has a case for signed-out
visitors, but the `/support` route sends them to sign-in first, so that case is
never reached; and `supportPopup` with its `.js-support` handler is no longer
opened by the menu, which links to `/support`. Decide whether signed-out
visitors should see the page, and remove the unused popup.
- Card menu / Create board from this card: the entry sits under `unless
canModifyCard` in `cardDetailsActionsPopup` (`client/components/cards/
cardDetails.jade`), so a member who can edit the card does not see it, while
the `createBoardFromCard` method requires write access. It was in both
branches when added (17c6d8d9b9); a later refactor kept only this one. Check in
the running app and restore it for members who can edit the card.
- Board menu / All Boards Settings: the board menu entry is commented out
("Bug Board icons random dance", [#4214](https://github.com/wekan/wekan/issues/4214)), so the popup cannot be reached.
- Admin Panel / People / Shared templates: which group kinds the "Share template
with" picker offers comes from the browser's `localStorage`
(`sharedTemplatesScopes`), so it differs per browser and is empty in a browser
where the admin never ticked them. An instance setting belongs in Settings.
+17 -7
View File
@@ -2400,7 +2400,10 @@ Template.cardDestinationPicker.helpers({
destinationError() { return Template.instance().dialog.error.get(); },
destinationDisabled() {
const dialog = Template.instance().dialog;
return dialog.loading.get() || dialog.saving.get() || !dialog.selectedSwimlaneId.get() || !dialog.selectedListId.get();
// #6917: and until the chosen list's cards are there, so a move or copy
// never places the card against a dropdown that has not filled yet.
return dialog.loading.get() || dialog.saving.get() || !!dialog.cardsLoading?.get()
|| !dialog.selectedSwimlaneId.get() || !dialog.selectedListId.get();
},
boards() {
return Template.instance().dialog.boards();
@@ -2465,7 +2468,7 @@ function registerCardDialogTemplate(templateName) {
async 'click .js-done'(event, tpl) {
event.preventDefault();
const dialog = tpl.dialog;
if (dialog.loading.get() || dialog.saving.get()) return;
if (dialog.loading.get() || dialog.saving.get() || dialog.cardsLoading?.get()) return;
// Read the target board/swimlane/list from the dialog's live reactive
// selection rather than the DOM <select> elements. A reactive re-render
// (e.g. the boards() helper transiently returning [] while a 'board'
@@ -2934,6 +2937,7 @@ Template.cardMorePopup.onCreated(function () {
// is no longer blank the first time another board is picked (the cards()
// helper queries minimongo, which was empty before the subscription arrived).
this.parentBoardReady = new ReactiveVar(true);
this.view.onViewDestroyed(() => this.parentCardsSubscription?.stop());
this.parentCard = this.currentCard?.parentCard();
if (this.parentCard) {
const list = $('.js-field-parent-card');
@@ -3080,11 +3084,17 @@ Template.cardMorePopup.events({
// #3745: wait for the board subscription to be ready before showing its
// cards, so the parent-card list is populated on the first selection.
tpl.parentBoardReady.set(false);
Meteor.subscribe('board', selection, false, {
onReady() {
tpl.parentBoardReady.set(true);
},
});
// #6917: a lazily loaded board's `board` publication ships no cards, so
// the parent-card list also subscribes to the board's card titles, and
// is ready when both are.
tpl.parentCardsSubscription?.stop();
let pending = 2;
const ready = () => {
pending -= 1;
if (pending === 0 && tpl.parentBoard.get() === selection) tpl.parentBoardReady.set(true);
};
Meteor.subscribe('board', selection, false, { onReady: ready });
tpl.parentCardsSubscription = Meteor.subscribe('destinationCards', selection, null, null, { onReady: ready });
tpl.parentBoard.set(selection);
list.prop('disabled', false);
}
+1 -1
View File
@@ -347,7 +347,7 @@ template(name="copyAndMoveChecklist")
option(value="{{_id}}" selected="{{#if isDialogOptionCardId _id}}selected{{/if}}") {{title}}
.edit-controls.clearfix
button.primary.confirm.js-done {{_ 'done'}}
button.primary.confirm.js-done(type="button" disabled=doneDisabled) {{_ 'done'}}
//- Due date on a single checklist item (#4755). The badge and its edit popup
reuse the card's own date-badge markup (dateBadgeBody) and date-picker form
+11
View File
@@ -841,6 +841,11 @@ Template.copyAndMoveChecklist.helpers({
const dialog = getParentDialog(Template.instance());
return dialog ? dialog.isTitleDefault(title) : title;
},
// #6917: Done waits for the destination list's cards.
doneDisabled() {
const dialog = getParentDialog(Template.instance());
return !dialog || dialog.loading.get() || dialog.cardsLoading.get() || dialog.cards().length === 0;
},
});
/**
@@ -865,6 +870,11 @@ function registerChecklistDialogEvents(templateName) {
? cardSelect.options[cardSelect.selectedIndex].value
: null;
// #6917: every checklist dialog needs a card, and the dropdown may still
// be filling: Done does nothing until a card of the list is chosen.
if (dialog.loading.get() || dialog.cardsLoading.get()) return;
if (!cardId || !dialog.cards().some(card => card._id === cardId)) return;
const options = { boardId, swimlaneId, listId, cardId };
try {
await dialog.setDone(cardId, options);
@@ -879,6 +889,7 @@ function registerChecklistDialogEvents(templateName) {
'change .js-select-swimlanes'(event, tpl) {
tpl.dialog.selectedSwimlaneId.set($(event.currentTarget).val());
tpl.dialog.setFirstListId();
tpl.dialog.selectedCardId.set('');
},
'change .js-select-lists'(event, tpl) {
tpl.dialog.selectedListId.set($(event.currentTarget).val());
+15
View File
@@ -665,6 +665,10 @@ Template.listBody.helpers({
// just this list/swimlane window (grows with `limit` as the user scrolls)
// plus its reactive total count. Default mode keeps everything in minimongo
// already, so these subscriptions are skipped.
// #6927: the board's archived swimlane ids, so the first swimlane does not
// take their cards as orphans (models/lib/archivedSwimlaneIds.js). One
// tiny document per board; identical subscriptions are shared.
if (list.boardId) tpl.subscribe('boardArchivedSwimlaneIds', list.boardId);
if (list.boardId && isLazyCards(list.boardId)) {
tpl.subscribe('boardCardsWindow', list.boardId, mongoSelector, sortBy, limit);
tpl.subscribe(
@@ -1209,6 +1213,17 @@ Template.linkCardPopup.onCreated(function () {
else if (Utils.boardView() === 'board-view-lists' || !Utils.boardView)
this.swimlaneId = listData.swimlaneId || ReactiveCache.getSwimlane({ boardId: this.boardId })._id;
// #6917: the cards offered for linking come from their own subscription. A
// lazily loaded board's `board` publication ships no cards, so a large board
// picked here listed none. Inside the autorun, the previous selection's
// subscription stops when another board, swimlane or list is chosen.
this.autorun(() => {
const boardId = this.selectedBoardId.get();
if (!boardId) return;
this.subscribe('destinationCards', boardId,
this.selectedListId.get() || null, this.selectedSwimlaneId.get() || null);
});
this.getSortIndex = () => {
let ret;
if (this.position === 'top') {
+13 -11
View File
@@ -253,10 +253,11 @@ template(name="listActionPopup")
a.js-select-cards
i.fa.fa-select-square
| {{_ 'list-select-cards'}}
li
a.js-archive-list-cards
i.fa.fa-archive
| {{_ 'list-archive-cards'}}
if mayWriteList
li
a.js-archive-list-cards
i.fa.fa-archive
| {{_ 'list-archive-cards'}}
if currentUser.isBoardAdmin
ul.pop-over-list
li
@@ -301,13 +302,14 @@ template(name="listActionPopup")
i.fa.fa-arrow-right
| {{_ 'moveListPopup-title'}}
unless currentUser.isWorker
hr
ul.pop-over-list
li
a.js-close-list
i.fa.fa-arrow-right
i.fa.fa-archive
| {{_ 'archive-list'}}
if mayWriteList
hr
ul.pop-over-list
li
a.js-close-list
i.fa.fa-arrow-right
i.fa.fa-archive
| {{_ 'archive-list'}}
hr
ul.pop-over-list
li
+11
View File
@@ -11,6 +11,7 @@ import { LIST_COLORS } from '/models/metadata/colors';
import { isHexColor, toHex } from '/models/lib/contrastColor';
import { MultiSelection } from '/client/lib/multiSelection';
import { Utils } from '/client/lib/utils';
import { listCan } from '/models/lib/listPermissions';
import { lazyListCardCount } from '/client/lib/lazyCards';
import { currentUserWith } from '/client/lib/currentUserWith';
import {
@@ -455,6 +456,16 @@ Template.listActionPopup.helpers({
return ReactiveCache.getCurrentUser()?.isBoardAdmin();
},
// Decided 2026-11-18 (TODO.md): a list that refuses the viewer's role a
// write (#4527) also refuses archiving it and archiving its cards, so the
// menu does not offer them (server/listPermissions.js refuses them anyway).
mayWriteList() {
const list = Template.currentData();
if (!list || !list.roleExceptions) return true;
const board = ReactiveCache.getBoard(list.boardId);
return !!(board && listCan(board, list, Meteor.userId(), 'write'));
},
isWipLimitEnabled() {
return Template.currentData().getWipLimit('enabled');
},
@@ -26,12 +26,6 @@ template(name="adminProblems")
+problemsSummary
else if isPane 'features-performance'
+featuresPerformance
else if isPane 'features-security'
+featuresSecurity
else if isPane 'features-delete'
+featuresDelete
else if isPane 'features-notifications'
+featuresNotifications
else if isPane 'features-backup'
+backupRunsStatus(settingsLink=true)
else if isPane 'report-security'
@@ -148,7 +142,7 @@ template(name="featuresPerformance")
.title {{_ 'cards-loading'}}
p.description {{_ 'cards-loading-description'}}
//- Admin Panel / Problems / Security.
//- Admin Panel / Settings / Security (moved from Problems on 2026-11-19).
template(name="featuresSecurity")
ul.setting-detail
li
@@ -192,7 +186,7 @@ template(name="featuresSecurity")
span {{_ 'anonymize-export-users'}}
p.description {{_ 'anonymize-export-users-description'}}
//- Admin Panel / Problems / Delete.
//- Admin Panel / Settings / Delete (moved from Problems on 2026-11-19).
template(name="featuresDelete")
ul.setting-detail
li
@@ -202,7 +196,7 @@ template(name="featuresDelete")
p.description {{_ 'enable-permanent-delete-description'}}
p.description {{permanentDeleteRecoveryDescription}}
//- Admin Panel / Problems / Notifications.
//- Admin Panel / Settings / Activities and notifications (moved from Problems on 2026-11-19).
template(name="featuresNotifications")
ul.setting-detail
li
+5 -14
View File
@@ -298,19 +298,10 @@ Template.adminProblems.onDestroyed(function () {
// are now the single .js-left-menu-item one below.
const PROBLEMS_MENU = [
{ id: 'report-summary', icon: 'fa-list', labelKey: 'summary' },
{ separator: true },
// Two groups, each named by a heading rather than by another entry: there is
// nothing to click on a group title (docs/Features/All-Boards/Left-Menu.md). Both use an
// i18n key the app already has.
{ heading: true, labelKey: 'settings' },
// Moved here from Admin Panel / Features. They are settings rather than reports -
// which is what this heading says - but they are what an admin reaches for when
// something is unsafe or noisy, which is what this page is about. Performance
// sits with the reports below, beside the Speed / Tests / CPU usage streams it is
// about.
{ id: 'features-security', icon: 'fa-shield', labelKey: 'features-security', emoji: true },
{ id: 'features-delete', icon: 'fa-trash', labelKey: 'delete' },
{ id: 'features-notifications', icon: 'fa-bell', labelKey: 'features-notifications', emoji: true },
// Security, Delete and Notifications were a "Settings" group here; they are
// settings, not problems, and moved to Admin Panel / Settings on 2026-11-19
// (Security, Activities and notifications, Delete). Their old addresses
// redirect there (models/lib/adminUrls.js MOVED_PANES).
// Did last night's backup work? The status and history of the Admin Panel
// backup (backupRunsStatus.jade), with a link to its settings in Attachments /
// Backup. A failed or overdue backup is also listed on Summary.
@@ -535,7 +526,7 @@ function switchMenu(event, tmpl) {
// nothing to fetch. Everything else falls through to loadReport().
const SELF_LOADING_PANES = [
'report-summary',
'features-performance', 'features-security', 'features-delete', 'features-notifications',
'features-performance',
// backupRunsStatus.jade loads its own data (the backupHistory method).
'features-backup',
'report-security', 'report-speed', 'report-tests', 'report-cpu', 'report-ram', 'report-disk',
@@ -187,6 +187,7 @@ template(name="orgRow")
| {{_ 'yes'}}
else
| {{_ 'no'}}
td.org-feature-profile {{featureProfileNames}}
td.text-center
input.js-toggle-org-feature(type="checkbox", data-feature="orgSharedTemplates", checked=orgData.orgSharedTemplates)
td.text-center
@@ -227,6 +228,7 @@ template(name="teamRow")
| {{_ 'yes'}}
else
| {{_ 'no'}}
td.team-feature-profile {{featureProfileNames}}
td.text-center
input.js-toggle-team-feature(type="checkbox", data-feature="teamSharedTemplates", checked=teamData.teamSharedTemplates)
td.text-center
@@ -285,6 +287,7 @@ template(name="peopleRow")
| {{_ 'yes'}}
else
| {{_ 'no'}}
td.people-feature-profile {{featureProfileName}}
td.account-active-status
if userData.loginDisabled
span.text-red.js-toggle-active-status(data-user-id=userData._id, data-is-active="false", title="{{_ 'admin-people-user-inactive'}}")
+36
View File
@@ -661,6 +661,10 @@ function peopleDocs(tpl) {
// that had no date and showed "-", although the people publication
// sends it.
lastConnectionDate: 1,
// #6837: the Feature profiles column decides from these three.
featureProfileId: 1,
teams: 1,
orgs: 1,
},
}).fetch();
// The server's order, not minimongo's: `$in` does not preserve it.
@@ -672,6 +676,9 @@ const PEOPLE_COLUMNS = [
{ labelKey: 'username' },
{ labelKey: 'email' },
{ labelKey: 'admin' },
// #6837: which feature profile applies to the person - edited in Admin Panel
// / Settings / Feature profiles, shown here so it can be found from People.
{ labelKey: 'feature-profiles' },
{ labelKey: 'active-person' },
{ labelKey: 'location' },
{ labelKey: 'accounts-lockout-status' },
@@ -697,6 +704,8 @@ const TEAM_COLUMNS = [
{ labelKey: 'website' },
{ labelKey: 'createdAt' },
{ labelKey: 'active-team' },
// #6837: the feature profiles assigned to this team (Settings / Feature profiles).
{ labelKey: 'feature-profiles' },
{ headerTemplate: 'teamFeatureHeader',
headerData: { labelKey: 'team-shared-templates', feature: 'teamSharedTemplates' } },
{ headerTemplate: 'teamFeatureHeader',
@@ -713,6 +722,8 @@ const ORG_COLUMNS = [
{ labelKey: 'website' },
{ labelKey: 'createdAt' },
{ labelKey: 'active-org' },
// #6837: the feature profiles assigned to this organization.
{ labelKey: 'feature-profiles' },
{ headerTemplate: 'orgFeatureHeader',
headerData: { labelKey: 'org-shared-templates', feature: 'orgSharedTemplates' } },
{ headerTemplate: 'orgFeatureHeader',
@@ -1599,19 +1610,44 @@ Template.templatesGeneral.events({
},
});
// #6837: the names of the feature profiles a team or organization is named in,
// in the page's order (the first applies to a member without their own), or '-'.
function groupProfileNames(field, id) {
const { storedProfiles } = require('/models/lib/featureProfiles');
const names = storedProfiles(ReactiveCache.getCurrentSetting())
.filter(profile => id && (profile[field] || []).includes(id)).map(profile => profile.name);
return names.length ? names.join(', ') : '-';
}
Template.orgRow.helpers({
orgData() {
return this.org || ReactiveCache.getOrg(this.orgId);
},
featureProfileNames() {
const org = this.org || ReactiveCache.getOrg(this.orgId);
return groupProfileNames('orgIds', org && org._id);
},
});
Template.teamRow.helpers({
teamData() {
return this.team || ReactiveCache.getTeam(this.teamId);
},
featureProfileNames() {
const team = this.team || ReactiveCache.getTeam(this.teamId);
return groupProfileNames('teamIds', team && team._id);
},
});
Template.peopleRow.helpers({
// #6837: the feature profile that applies to this person, or '-'.
featureProfileName() {
// The row's user, found the way userData below finds it.
const id = this._id || (this.user && this.user._id);
const doc = (id && ReactiveCache.getUser(id)) || this.user || null;
const profile = require('/models/lib/featureProfiles').profileForUser(ReactiveCache.getCurrentSetting(), doc);
return profile ? profile.name : '-';
},
loginCountries() {
const userId = this.user && this.user._id;
return (this.countries || []).map(country => ({ ...country, userId }));
@@ -97,7 +97,7 @@ template(name="problemsSummary")
input.js-problem-check(type="checkbox" data-stream="{{area.stream}}")
i.fa.fa-exclamation-triangle
span.admin-problem-path {{_ 'admin-panel'}} → {{_ 'problems'}} → {{areaLabel area.stream}}
span.admin-problem-count {{area.count}} {{_ 'new-problems'}}
span.admin-problem-count {{_ 'new-problems-count' count=area.count}}
.admin-problem-actions
button.js-ack-checked.primary {{_ 'acknowledge'}}
button.js-clear-checked {{_ 'clear-problems'}}
@@ -104,9 +104,11 @@ Template.problemsSummary.helpers({
// A key of its own: List Sync's "never synced" may be translated as
// "never synced", which reads wrong beside "Last Run".
if (!d || !d.at) return TAPi18n.__('data-health-never-run');
// "<when> - <checks that found something>/<checks>"
// "<when> - Checks with findings: <found> / <checks>". A bare "8/31"
// left the admin guessing what was counted.
const at = new Date(d.at).toISOString().replace('T', ' ').slice(0, 16) + ' UTC';
const text = `${at} - ${d.found}/${d.checks}`;
const found = TAPi18n.__('data-health-checks-found', { found: d.found, checks: d.checks });
const text = `${at} - ${found}`;
return d.error ? `${text} - ${d.error}` : text;
},
repairRunning() {
+375 -326
View File
@@ -26,7 +26,20 @@ template(name="setting")
//- templates are global, so the pane renders here.
+statistics
else if isTableVisibilityModeSetting
+tableVisibilityModeSettings
//- Security, Activities and notifications and Delete below moved
here from Admin Panel / Problems (2026-11-19); their templates and
handlers stay in adminProblems.jade / adminProblems.js.
+tableVisibilityModeSettings(part="appearance")
else if isFeaturesSetting
+tableVisibilityModeSettings(part="features")
else if isFeatureProfilesSetting
+tableVisibilityModeSettings(part="profiles")
else if isPrivacySecuritySetting
+featuresSecurity
else if isActivitiesSetting
+featuresNotifications
else if isDeleteSetting
+featuresDelete
else if isAnnouncementSetting
+announcementSettings
else if isAccessibilitySetting
@@ -322,335 +335,371 @@ template(name='email')
//- groups under it rather than as several pages.
template(name='tableVisibilityModeSettings')
ul#tableVisibilityMode-setting.setting-detail
//- Every group here writes the INSTANCE settings, so it is site-admin only.
//- The one exception is "Change color" below, which an Organization's own
//- admin sets for their Organization (models/lib/tenantAdmin.js themeTarget).
if isSiteAdmin
li
h2.admin-pane-group-title {{_ 'all-boards-hide'}}
//- One checkbox per setting instead of a Yes/No pair: each of these is on or
//- off, and the group's own title already says what ticking one means (All
//- Boards: Hide …). Same checkbox as everywhere else in the Admin Panel -
//- Announcement's "Active System-Wide Announcement" - so it has the plain
//- square when off, the green tick when on, and the animation between.
//- The Save button below reads the ticks, as it read the radios.
li.tableVisibilityMode-form
//- "Public boards", under the "All Boards: Hide" title above: ticked hides
//- them, which is what allowPrivateOnly does. The setting's own key keeps its
//- sentence - boardBody.jade shows it as the message on a board you may not
//- open, where a two-word label would say nothing.
a.flex.js-toggle-all-boards-hide
.materialCheckBox#accounts-allowPrivateOnly(class="{{#if allowPrivateOnly}}is-checked{{/if}}")
span {{_ 'public-boards'}}
li.tableVisibilityMode-form
//- #4475: ticked forbids anyone who is not a site admin from creating
//- new boards. Same Save button and same collection as the setting
//- above - only the checked key differs.
a.flex.js-toggle-all-boards-hide
.materialCheckBox#accounts-boardCreationAdminOnly(class="{{#if boardCreationAdminOnly}}is-checked{{/if}}")
span {{_ 'board-creation-admin-only'}}
li.tableVisibilityMode-form
//- #4575: ticked lets a board admin open an Instance or Public board
//- to editing by every signed-in user. Off: no board can.
a.flex.js-toggle-all-boards-hide
.materialCheckBox#accounts-allowInstanceEditing(class="{{#if allowInstanceEditing}}is-checked{{/if}}")
span {{_ 'instance-editing-allowed'}}
li.hideBoardActivities-form
a.flex.js-toggle-all-boards-hide
.materialCheckBox#hide-board-activities(class="{{#if currentSetting.hideBoardActivitiesOnAllBoards}}is-checked{{/if}}")
span {{_ 'board-activities'}}
li.tableVisibilityMode-form
a.flex.js-toggle-all-boards-hide
.materialCheckBox#hide-card-counter-list(class="{{#if currentSetting.hideCardCounterList}}is-checked{{/if}}")
span {{_ 'card-counter-list'}}
li.tableVisibilityMode-form
a.flex.js-toggle-all-boards-hide
.materialCheckBox#hide-board-member-list(class="{{#if currentSetting.hideBoardMemberList}}is-checked{{/if}}")
span {{_ 'board-member-list'}}
li.tableVisibilityMode-form
.title {{_ 'wait-spinner'}}
+selectSpinnerName(spinnerName=currentSetting.spinnerName)
//- #4421: an org whose "Public" means "public within our organization"
//- rather than public on the internet can replace the wording shown
//- under Private/Public in the board visibility popup and the
//- create-board popup. Empty = unchanged i18n default text
//- (imports/i18n/lib/visibilityDesc.js).
li.tableVisibilityMode-form
.title {{_ 'custom-private-desc'}}
.form-group
textarea.wekan-form-control#custom-private-board-desc(data-editor-submit=".js-visibility-all-boards-save" rows="2" placeholder="{{_ 'custom-private-desc-placeholder'}}")= currentSetting.customPrivateBoardDesc
li.tableVisibilityMode-form
.title {{_ 'custom-public-desc'}}
.form-group
textarea.wekan-form-control#custom-public-board-desc(data-editor-submit=".js-visibility-all-boards-save" rows="2" placeholder="{{_ 'custom-public-desc-placeholder'}}")= currentSetting.customPublicBoardDesc
li
//- One Save per section, at its end, above the rule that closes it. It writes
//- this section's fields and nothing else, so saving one group can never
//- overwrite what you were editing in another.
button.js-visibility-all-boards-save.primary {{_ 'save'}}
li.admin-pane-group-separator
hr
//- #6736: which optional features this WeKan offers. A ticked feature is
//- on for everyone; an unticked one is hidden from the interface (not
//- greyed out), keeps its data, and changes no permission. The rows come
//- from models/lib/instanceFeatures.js, so the page and the places that
//- hide a feature read the same catalog.
li
h2.admin-pane-group-title {{_ 'features'}}
li.tableVisibilityMode-form
.title {{_ 'features-desc'}}
each featureRows
li.tableVisibilityMode-form.js-feature-row(data-feature=key)
a.flex.js-toggle-feature
.materialCheckBox.js-feature-enabled(class="{{#if enabled}}is-checked{{/if}}")
span {{_ labelKey}}
if awaitingApproval
span.feature-awaiting-approval {{_ 'feature-awaiting-approval'}}
.feature-desc {{_ descKey}}
li.tableVisibilityMode-form
a.flex.js-toggle-feature
.materialCheckBox#feature-approval-required(class="{{#if currentSetting.featureApprovalRequired}}is-checked{{/if}}")
span {{_ 'feature-approval-required'}}
li.tableVisibilityMode-form
a.flex.js-toggle-feature
.materialCheckBox#feature-preview-admins(class="{{#if currentSetting.featurePreviewAdmins}}is-checked{{/if}}")
span {{_ 'feature-preview-admins'}}
li.tableVisibilityMode-form
.title {{_ 'feature-pilot-users'}}
.form-group
textarea.wekan-form-control#feature-pilot-users(data-editor-submit=".js-visibility-features-save" rows="2" placeholder="{{_ 'feature-pilot-users-placeholder'}}")= featurePilotUsernames
//- The card fields every board shows: one tick per field type of Board
//- Settings / Card, all ticked by default. Unticked hides it on every
//- card, minicard and Board Settings / Card - visibility only, no data or
//- board setting changes. No ordering here: the order is each board's own.
//- models/lib/cardFieldVisibility.js
li.tableVisibilityMode-form
.title {{_ 'card-field-visibility'}}
.feature-desc {{_ 'card-field-visibility-desc'}}
each cardFieldRows
li.tableVisibilityMode-form.js-card-field-row(data-card-field=key)
a.flex.js-toggle-feature
.materialCheckBox.js-card-field-enabled(class="{{#if enabled}}is-checked{{/if}}")
span.card-field-visibility-label
each icon in icons
i.fa(class=icon)
| {{title}}
li
button.js-visibility-features-save.primary {{_ 'save'}}
span.js-visibility-features-status
//- #2460: SQRL sign-in, and #4198: public boards on the fediverse
(ActivityPub) - optional features this WeKan offers, each off by
default and saved as soon as it is switched.
li.tableVisibilityMode-form
a.flex.js-toggle-sqrl
.materialCheckBox#sqrl-enabled(class="{{#if currentSetting.sqrlEnabled}}is-checked{{/if}}")
span {{_ 'sqrl-enabled'}}
.feature-desc {{_ 'sqrl-desc'}}
li.tableVisibilityMode-form
a.flex.js-toggle-activity-pub
.materialCheckBox#activity-pub-enabled(class="{{#if currentSetting.activityPubEnabled}}is-checked{{/if}}")
span {{_ 'activity-pub-enabled'}}
.feature-desc {{_ 'activity-pub-desc'}}
li.admin-pane-group-separator
hr
//- #2217: boards may show their Rules to members, read-only. Off by
default; each board admin then decides on the board's Rules page.
li
h2.admin-pane-group-title {{_ 'rules'}}
li.tableVisibilityMode-form
a.flex.js-toggle-rules-read-only
.materialCheckBox#rules-read-only-for-members(class="{{#if currentSetting.rulesReadOnlyForMembers}}is-checked{{/if}}")
span {{_ 'rules-read-only-for-members'}}
.feature-desc {{_ 'rules-read-only-for-members-desc'}}
li.admin-pane-group-separator
hr
//- Optional APIs (models/lib/optionalApis.js): REST APIs in the shape of
Trello's, Jira's, GitHub's and Gitea's, so their clients can use WeKan
as their backend. Each is off until ticked, and has no rights of its
own: it is WeKan's REST API, with the caller's own permissions.
li
h2.admin-pane-group-title {{_ 'optional-apis'}}
li.tableVisibilityMode-form
.title {{_ 'optional-apis-desc'}}
each optionalApiRows
li.tableVisibilityMode-form.js-optional-api-row(data-api=key)
a.flex.js-toggle-feature
.materialCheckBox.js-optional-api-enabled(class="{{#if enabled}}is-checked{{/if}}")
span {{_ labelKey}}
.feature-desc {{_ descKey}}
.feature-desc
code {{base}}
li
button.js-optional-apis-save.primary {{_ 'save'}}
span.js-optional-apis-status
li.admin-pane-group-separator
hr
li
h2.admin-pane-group-title {{_ 'date'}}
li.tableVisibilityMode-form
a.flex.js-toggle-date-format
.materialCheckBox#global-date-format-enabled(class="{{#if currentSetting.hideDateFormat}}is-checked{{/if}}")
span {{_ 'date-format'}}:
select.wekan-form-control#global-date-format(aria-label="{{_ 'date-format'}}")
option(value="YYYY-MM-DD" selected="{{#if isGlobalDateFormat 'YYYY-MM-DD'}}selected{{/if}}") {{_ 'date-format-yyyy-mm-dd'}} · {{_ 'time'}}
option(value="DD-MM-YYYY" selected="{{#if isGlobalDateFormat 'DD-MM-YYYY'}}selected{{/if}}") {{_ 'date-format-dd-mm-yyyy'}} · {{_ 'time'}}
option(value="MM-DD-YYYY" selected="{{#if isGlobalDateFormat 'MM-DD-YYYY'}}selected{{/if}}") {{_ 'date-format-mm-dd-yyyy'}} · {{_ 'time'}}
option(value="YYYY-MM-DD-date-only" selected="{{#if isGlobalDateFormat 'YYYY-MM-DD-date-only'}}selected{{/if}}") {{_ 'date'}}: {{_ 'date-format-yyyy-mm-dd'}}
option(value="DD-MM-YYYY-date-only" selected="{{#if isGlobalDateFormat 'DD-MM-YYYY-date-only'}}selected{{/if}}") {{_ 'date'}}: {{_ 'date-format-dd-mm-yyyy'}}
option(value="MM-DD-YYYY-date-only" selected="{{#if isGlobalDateFormat 'MM-DD-YYYY-date-only'}}selected{{/if}}") {{_ 'date'}}: {{_ 'date-format-mm-dd-yyyy'}}
li
button.js-visibility-date-save.primary {{_ 'save'}}
li.admin-pane-group-separator
hr
li
h2.admin-pane-group-title {{_ 'settings-group-url'}}
li
a(href="/support" style="text-decoration: underline; color: blue;") {{_ 'support'}}
li
a.flex.js-toggle-support
.materialCheckBox(class="{{#if currentSetting.supportPageEnabled}}is-checked{{/if}}")
span {{_ 'support-page-enabled'}}
li
.support-content(class="{{#if currentSetting.supportPageEnabled}}{{else}}hide{{/if}}")
ul
li
a.flex.js-toggle-support-public
.materialCheckBox(class="{{#if currentSetting.supportPagePublic}}is-checked{{/if}}")
span {{_ 'public'}}
li
.title {{_ 'support-title'}}
textarea#support-title.wekan-form-control(data-editor-submit=".js-visibility-url-save")= currentSetting.supportTitle
li
.title {{_ 'support-content'}}
textarea#support-page-text.wekan-form-control(data-editor-submit=".js-visibility-url-save")= currentSetting.supportPageText
li.tableVisibilityMode-form
.title {{_ 'custom-help-link-url'}}
.form-group
input.wekan-form-control#custom-help-link-url(type="text", placeholder="" value="{{currentSetting.customHelpLinkUrl}}")
li.tableVisibilityMode-form
.title {{_ 'custom-legal-notice-link-url'}}
.form-group
input.wekan-form-control#legalNoticevalue(type="text", placeholder="" value="{{currentSetting.legalNotice}}")
li.tableVisibilityMode-form
.title {{_ 'automatic-linked-url-schemes'}}
.description {{_ 'automatic-linked-url-schemes-hint'}}
.form-group
textarea#automatic-linked-url-schemes.wekan-form-control(data-editor-submit=".js-visibility-url-save")= currentSetting.automaticLinkedUrlSchemes
li
button.js-visibility-url-save.primary {{_ 'save'}}
li.admin-pane-group-separator
hr
li
//- wekan/wekan#3069: autolink bare "<prefix>NNNN" tokens (e.g. "#1234")
//- found in card descriptions/comments to an external issue tracker.
//- Leaving either field empty keeps this feature off (no-op).
h2.admin-pane-group-title {{_ 'external-link-pattern'}}
p.description {{_ 'external-link-pattern-description'}}
li.tableVisibilityMode-form
.title {{_ 'external-link-pattern-prefix'}}
.form-group
input.wekan-form-control#external-link-pattern-prefix(type="text", placeholder="#" value="{{currentSetting.externalLinkPatternPrefix}}")
li.tableVisibilityMode-form
.title {{_ 'external-link-pattern-url'}}
.form-group
input.wekan-form-control#external-link-pattern-url(type="text", placeholder="https://issues.example.com/browse/PROJ-{number}" value="{{currentSetting.externalLinkPatternUrl}}")
//- #1463: more rules, with {identifier}, and abbreviations for it.
li.tableVisibilityMode-form
.title {{_ 'external-link-rules'}}
p.description {{_ 'external-link-rules-description'}}
.form-group
textarea.wekan-form-control#external-link-rules(rows="4" placeholder="[{identifier}:{number}] = https://spirateam.example.com/SpiraTeam/{identifier}/{number}.aspx")= currentSetting.externalLinkRules
li.tableVisibilityMode-form
.title {{_ 'external-link-identifier-aliases'}}
.form-group
input.wekan-form-control#external-link-identifier-aliases(type="text", placeholder="TK=Task, IN=Incident" value="{{currentSetting.externalLinkIdentifierAliases}}")
li
button.js-visibility-external-link-pattern-save.primary {{_ 'save'}}
li.admin-pane-group-separator
hr
li
//- The group title IS the field's label here: the group holds one field, so a
//- title above a label that says the same thing said it twice. The group title
//- keeps its size and takes the field's existing translation.
h2.admin-pane-group-title {{_ 'custom-product-name'}}
li.tableVisibilityMode-form
.form-group
textarea.wekan-form-control#product-name(data-editor-submit=".js-visibility-product-name-save" rows="2" placeholder="")= currentSetting.productName
li
button.js-visibility-product-name-save.primary {{_ 'save'}}
//- The site theme. Same picker as the per-user "Change color", one layer
//- below it: whoever has not chosen a theme of their own sees this one
//- (docs/Theme/Theme.md). It applies immediately - the picker has no Save
//- button, like the per-user one.
if isSiteAdmin
li.admin-pane-group-separator
hr
li
h2.admin-pane-group-title {{_ 'change-color'}}
//- The site admin's colour is the one every Organization that has not set
//- its own inherits, so their pane says so; an Organization's own admin is
//- setting only their own and needs no such line.
//- Three panes of Admin Panel / Settings share this template and its
//- handlers (2026-11-19): Appearance, Features and Feature profiles. `part`
//- says which groups this pane shows; every field keeps its id and its Save.
if isPart 'features'
if isSiteAdmin
h3.admin-pane-subgroup-title {{_ 'theme-override-all-tenants'}}
li.tableVisibilityMode-form
+themeColorPicker(scope="admin")
//- #6736: which optional features this WeKan offers. A ticked feature is
//- on for everyone; an unticked one is hidden from the interface (not
//- greyed out), keeps its data, and changes no permission. The rows come
//- from models/lib/instanceFeatures.js, so the page and the places that
//- hide a feature read the same catalog.
li
h2.admin-pane-group-title {{_ 'features'}}
li.tableVisibilityMode-form
.title {{_ 'features-desc'}}
each featureRows
li.tableVisibilityMode-form.js-feature-row(data-feature=key)
a.flex.js-toggle-feature
.materialCheckBox.js-feature-enabled(class="{{#if enabled}}is-checked{{/if}}")
span {{_ labelKey}}
if awaitingApproval
span.feature-awaiting-approval {{_ 'feature-awaiting-approval'}}
.feature-desc {{_ descKey}}
li.tableVisibilityMode-form
a.flex.js-toggle-feature
.materialCheckBox#feature-approval-required(class="{{#if currentSetting.featureApprovalRequired}}is-checked{{/if}}")
span {{_ 'feature-approval-required'}}
li.tableVisibilityMode-form
a.flex.js-toggle-feature
.materialCheckBox#feature-preview-admins(class="{{#if currentSetting.featurePreviewAdmins}}is-checked{{/if}}")
span {{_ 'feature-preview-admins'}}
li.tableVisibilityMode-form
.title {{_ 'feature-pilot-users'}}
.form-group
textarea.wekan-form-control#feature-pilot-users(data-editor-submit=".js-visibility-features-save" rows="2" placeholder="{{_ 'feature-pilot-users-placeholder'}}")= featurePilotUsernames
//- The card fields every board shows: one tick per field type of Board
//- Settings / Card, all ticked by default. Unticked hides it on every
//- card, minicard and Board Settings / Card - visibility only, no data or
//- board setting changes. No ordering here: the order is each board's own.
//- models/lib/cardFieldVisibility.js
li.tableVisibilityMode-form
.title {{_ 'card-field-visibility'}}
.feature-desc {{_ 'card-field-visibility-desc'}}
each cardFieldRows
li.tableVisibilityMode-form.js-card-field-row(data-card-field=key)
a.flex.js-toggle-feature
.materialCheckBox.js-card-field-enabled(class="{{#if enabled}}is-checked{{/if}}")
span.card-field-visibility-label
each icon in icons
i.fa(class=icon)
| {{title}}
li
button.js-visibility-features-save.primary {{_ 'save'}}
span.js-visibility-features-status
if isSiteAdmin
li.admin-pane-group-separator
hr
//- #2460: SQRL sign-in, and #4198: public boards on the fediverse
(ActivityPub) - optional features this WeKan offers, each off by
default and saved as soon as it is switched.
li.tableVisibilityMode-form
a.flex.js-toggle-sqrl
.materialCheckBox#sqrl-enabled(class="{{#if currentSetting.sqrlEnabled}}is-checked{{/if}}")
span {{_ 'sqrl-enabled'}}
.feature-desc {{_ 'sqrl-desc'}}
li.tableVisibilityMode-form
a.flex.js-toggle-activity-pub
.materialCheckBox#activity-pub-enabled(class="{{#if currentSetting.activityPubEnabled}}is-checked{{/if}}")
span {{_ 'activity-pub-enabled'}}
.feature-desc {{_ 'activity-pub-desc'}}
li.admin-pane-group-separator
hr
//- #2217: boards may show their Rules to members, read-only. Off by
default; each board admin then decides on the board's Rules page.
li
h2.admin-pane-group-title {{_ 'rules'}}
li.tableVisibilityMode-form
a.flex.js-toggle-rules-read-only
.materialCheckBox#rules-read-only-for-members(class="{{#if currentSetting.rulesReadOnlyForMembers}}is-checked{{/if}}")
span {{_ 'rules-read-only-for-members'}}
.feature-desc {{_ 'rules-read-only-for-members-desc'}}
li.admin-pane-group-separator
hr
//- Optional APIs (models/lib/optionalApis.js): REST APIs in the shape of
Trello's, Jira's, GitHub's and Gitea's, so their clients can use WeKan
as their backend. Each is off until ticked, and has no rights of its
own: it is WeKan's REST API, with the caller's own permissions.
li
h2.admin-pane-group-title {{_ 'optional-apis'}}
li.tableVisibilityMode-form
.title {{_ 'optional-apis-desc'}}
each optionalApiRows
li.tableVisibilityMode-form.js-optional-api-row(data-api=key)
a.flex.js-toggle-feature
.materialCheckBox.js-optional-api-enabled(class="{{#if enabled}}is-checked{{/if}}")
span {{_ labelKey}}
.feature-desc {{_ descKey}}
.feature-desc
code {{base}}
li
button.js-optional-apis-save.primary {{_ 'save'}}
span.js-optional-apis-status
else if isPart 'profiles'
if isSiteAdmin
//- #6837: feature profiles - named sets of the features above that their
users do not see, assigned to users, teams or organizations. Opt-in: a
user with no profile sees everything, and a user with one is told so
(models/lib/featureProfiles.js). Visibility only, like the ticks above.
li.tableVisibilityMode-form
.title {{_ 'feature-profiles'}}
.feature-desc {{_ 'feature-profiles-desc'}}
each profile in featureProfileRows
li.tableVisibilityMode-form.js-feature-profile(data-profile-id=profile._id)
.form-group
label {{_ 'feature-profile-name'}}
input.wekan-form-control.js-feature-profile-name(type="text" value=profile.name maxlength="100")
.title {{_ 'feature-profile-hides'}}
each row in profile.rows
a.flex.js-toggle-feature.js-feature-profile-hide(data-feature=row.key)
.materialCheckBox(class="{{#if row.hidden}}is-checked{{/if}}")
span {{_ row.labelKey}}
.form-group
label {{_ 'feature-profile-users'}}
textarea.wekan-form-control.js-feature-profile-users(rows="2" placeholder="{{_ 'feature-pilot-users-placeholder'}}")= profile.usernames
.form-group
label {{_ 'feature-profile-teams'}}
textarea.wekan-form-control.js-feature-profile-teams(rows="2")= profile.teams
.form-group
label {{_ 'feature-profile-orgs'}}
textarea.wekan-form-control.js-feature-profile-orgs(rows="2")= profile.orgs
button.js-feature-profile-remove(type="button") {{_ 'feature-profile-remove'}}
li
button.js-feature-profile-add(type="button") {{_ 'feature-profile-add'}}
button.js-feature-profiles-save.primary(type="button") {{_ 'save'}}
span.js-feature-profiles-status
else
//- Every group here writes the INSTANCE settings, so it is site-admin only.
//- The one exception is "Change color" below, which an Organization's own
//- admin sets for their Organization (models/lib/tenantAdmin.js themeTarget).
if isSiteAdmin
li
h2.admin-pane-group-title {{_ 'all-boards-hide'}}
//- One checkbox per setting instead of a Yes/No pair: each of these is on or
//- off, and the group's own title already says what ticking one means (All
//- Boards: Hide …). Same checkbox as everywhere else in the Admin Panel -
//- Announcement's "Active System-Wide Announcement" - so it has the plain
//- square when off, the green tick when on, and the animation between.
//- The Save button below reads the ticks, as it read the radios.
li.tableVisibilityMode-form
//- "Public boards", under the "All Boards: Hide" title above: ticked hides
//- them, which is what allowPrivateOnly does. The setting's own key keeps its
//- sentence - boardBody.jade shows it as the message on a board you may not
//- open, where a two-word label would say nothing.
a.flex.js-toggle-all-boards-hide
.materialCheckBox#accounts-allowPrivateOnly(class="{{#if allowPrivateOnly}}is-checked{{/if}}")
span {{_ 'public-boards'}}
li.tableVisibilityMode-form
//- #4475: ticked forbids anyone who is not a site admin from creating
//- new boards. Same Save button and same collection as the setting
//- above - only the checked key differs.
a.flex.js-toggle-all-boards-hide
.materialCheckBox#accounts-boardCreationAdminOnly(class="{{#if boardCreationAdminOnly}}is-checked{{/if}}")
span {{_ 'board-creation-admin-only'}}
li.tableVisibilityMode-form
//- #4575: ticked lets a board admin open an Instance or Public board
//- to editing by every signed-in user. Off: no board can.
a.flex.js-toggle-all-boards-hide
.materialCheckBox#accounts-allowInstanceEditing(class="{{#if allowInstanceEditing}}is-checked{{/if}}")
span {{_ 'instance-editing-allowed'}}
li.hideBoardActivities-form
a.flex.js-toggle-all-boards-hide
.materialCheckBox#hide-board-activities(class="{{#if currentSetting.hideBoardActivitiesOnAllBoards}}is-checked{{/if}}")
span {{_ 'board-activities'}}
li.tableVisibilityMode-form
a.flex.js-toggle-all-boards-hide
.materialCheckBox#hide-card-counter-list(class="{{#if currentSetting.hideCardCounterList}}is-checked{{/if}}")
span {{_ 'card-counter-list'}}
li.tableVisibilityMode-form
a.flex.js-toggle-all-boards-hide
.materialCheckBox#hide-board-member-list(class="{{#if currentSetting.hideBoardMemberList}}is-checked{{/if}}")
span {{_ 'board-member-list'}}
li.tableVisibilityMode-form
.title {{_ 'wait-spinner'}}
+selectSpinnerName(spinnerName=currentSetting.spinnerName)
//- #4421: an org whose "Public" means "public within our organization"
//- rather than public on the internet can replace the wording shown
//- under Private/Public in the board visibility popup and the
//- create-board popup. Empty = unchanged i18n default text
//- (imports/i18n/lib/visibilityDesc.js).
li.tableVisibilityMode-form
.title {{_ 'custom-private-desc'}}
.form-group
textarea.wekan-form-control#custom-private-board-desc(data-editor-submit=".js-visibility-all-boards-save" rows="2" placeholder="{{_ 'custom-private-desc-placeholder'}}")= currentSetting.customPrivateBoardDesc
li.tableVisibilityMode-form
.title {{_ 'custom-public-desc'}}
.form-group
textarea.wekan-form-control#custom-public-board-desc(data-editor-submit=".js-visibility-all-boards-save" rows="2" placeholder="{{_ 'custom-public-desc-placeholder'}}")= currentSetting.customPublicBoardDesc
li
//- One Save per section, at its end, above the rule that closes it. It writes
//- this section's fields and nothing else, so saving one group can never
//- overwrite what you were editing in another.
button.js-visibility-all-boards-save.primary {{_ 'save'}}
li.admin-pane-group-separator
hr
li
h2.admin-pane-group-title {{_ 'date'}}
li.tableVisibilityMode-form
a.flex.js-toggle-date-format
.materialCheckBox#global-date-format-enabled(class="{{#if currentSetting.hideDateFormat}}is-checked{{/if}}")
span {{_ 'date-format'}}:
select.wekan-form-control#global-date-format(aria-label="{{_ 'date-format'}}")
option(value="YYYY-MM-DD" selected="{{#if isGlobalDateFormat 'YYYY-MM-DD'}}selected{{/if}}") {{_ 'date-format-yyyy-mm-dd'}} · {{_ 'time'}}
option(value="DD-MM-YYYY" selected="{{#if isGlobalDateFormat 'DD-MM-YYYY'}}selected{{/if}}") {{_ 'date-format-dd-mm-yyyy'}} · {{_ 'time'}}
option(value="MM-DD-YYYY" selected="{{#if isGlobalDateFormat 'MM-DD-YYYY'}}selected{{/if}}") {{_ 'date-format-mm-dd-yyyy'}} · {{_ 'time'}}
option(value="YYYY-MM-DD-date-only" selected="{{#if isGlobalDateFormat 'YYYY-MM-DD-date-only'}}selected{{/if}}") {{_ 'date'}}: {{_ 'date-format-yyyy-mm-dd'}}
option(value="DD-MM-YYYY-date-only" selected="{{#if isGlobalDateFormat 'DD-MM-YYYY-date-only'}}selected{{/if}}") {{_ 'date'}}: {{_ 'date-format-dd-mm-yyyy'}}
option(value="MM-DD-YYYY-date-only" selected="{{#if isGlobalDateFormat 'MM-DD-YYYY-date-only'}}selected{{/if}}") {{_ 'date'}}: {{_ 'date-format-mm-dd-yyyy'}}
li
button.js-visibility-date-save.primary {{_ 'save'}}
li.admin-pane-group-separator
hr
li
h2.admin-pane-group-title {{_ 'settings-group-url'}}
li
a(href="/support" style="text-decoration: underline; color: blue;") {{_ 'support'}}
li
a.flex.js-toggle-support
.materialCheckBox(class="{{#if currentSetting.supportPageEnabled}}is-checked{{/if}}")
span {{_ 'support-page-enabled'}}
li
.support-content(class="{{#if currentSetting.supportPageEnabled}}{{else}}hide{{/if}}")
ul
li
a.flex.js-toggle-support-public
.materialCheckBox(class="{{#if currentSetting.supportPagePublic}}is-checked{{/if}}")
span {{_ 'public'}}
li
.title {{_ 'support-title'}}
textarea#support-title.wekan-form-control(data-editor-submit=".js-visibility-url-save")= currentSetting.supportTitle
li
.title {{_ 'support-content'}}
textarea#support-page-text.wekan-form-control(data-editor-submit=".js-visibility-url-save")= currentSetting.supportPageText
li.tableVisibilityMode-form
.title {{_ 'custom-help-link-url'}}
.form-group
input.wekan-form-control#custom-help-link-url(type="text", placeholder="" value="{{currentSetting.customHelpLinkUrl}}")
li.tableVisibilityMode-form
.title {{_ 'custom-legal-notice-link-url'}}
.form-group
input.wekan-form-control#legalNoticevalue(type="text", placeholder="" value="{{currentSetting.legalNotice}}")
li.tableVisibilityMode-form
.title {{_ 'automatic-linked-url-schemes'}}
.description {{_ 'automatic-linked-url-schemes-hint'}}
.form-group
textarea#automatic-linked-url-schemes.wekan-form-control(data-editor-submit=".js-visibility-url-save")= currentSetting.automaticLinkedUrlSchemes
li
button.js-visibility-url-save.primary {{_ 'save'}}
li.admin-pane-group-separator
hr
li
//- wekan/wekan#3069: autolink bare "<prefix>NNNN" tokens (e.g. "#1234")
//- found in card descriptions/comments to an external issue tracker.
//- Leaving either field empty keeps this feature off (no-op).
h2.admin-pane-group-title {{_ 'external-link-pattern'}}
p.description {{_ 'external-link-pattern-description'}}
li.tableVisibilityMode-form
.title {{_ 'external-link-pattern-prefix'}}
.form-group
input.wekan-form-control#external-link-pattern-prefix(type="text", placeholder="#" value="{{currentSetting.externalLinkPatternPrefix}}")
li.tableVisibilityMode-form
.title {{_ 'external-link-pattern-url'}}
.form-group
input.wekan-form-control#external-link-pattern-url(type="text", placeholder="https://issues.example.com/browse/PROJ-{number}" value="{{currentSetting.externalLinkPatternUrl}}")
//- #1463: more rules, with {identifier}, and abbreviations for it.
li.tableVisibilityMode-form
.title {{_ 'external-link-rules'}}
p.description {{_ 'external-link-rules-description'}}
.form-group
textarea.wekan-form-control#external-link-rules(rows="4" placeholder="[{identifier}:{number}] = https://spirateam.example.com/SpiraTeam/{identifier}/{number}.aspx")= currentSetting.externalLinkRules
li.tableVisibilityMode-form
.title {{_ 'external-link-identifier-aliases'}}
.form-group
input.wekan-form-control#external-link-identifier-aliases(type="text", placeholder="TK=Task, IN=Incident" value="{{currentSetting.externalLinkIdentifierAliases}}")
li
button.js-visibility-external-link-pattern-save.primary {{_ 'save'}}
li.admin-pane-group-separator
hr
li
//- The group title IS the field's label here: the group holds one field, so a
//- title above a label that says the same thing said it twice. The group title
//- keeps its size and takes the field's existing translation.
h2.admin-pane-group-title {{_ 'custom-product-name'}}
li.tableVisibilityMode-form
.form-group
textarea.wekan-form-control#product-name(data-editor-submit=".js-visibility-product-name-save" rows="2" placeholder="")= currentSetting.productName
li
button.js-visibility-product-name-save.primary {{_ 'save'}}
//- The site theme. Same picker as the per-user "Change color", one layer
//- below it: whoever has not chosen a theme of their own sees this one
//- (docs/Theme/Theme.md). It applies immediately - the picker has no Save
//- button, like the per-user one.
if isSiteAdmin
li.admin-pane-group-separator
hr
li
h2.admin-pane-group-title {{_ 'settings-group-logo'}}
h2.admin-pane-group-title {{_ 'change-color'}}
//- The site admin's colour is the one every Organization that has not set
//- its own inherits, so their pane says so; an Organization's own admin is
//- setting only their own and needs no such line.
if isSiteAdmin
h3.admin-pane-subgroup-title {{_ 'theme-override-all-tenants'}}
li.tableVisibilityMode-form
//- One checkbox, like the All Boards group above and like Announcement's
//- "Active System-Wide Announcement": ticked = the logo is hidden. The
//- group's Save below writes it, as it wrote the Yes/No pair.
a.flex.js-toggle-hide-logo
.materialCheckBox#hide-logo(class="{{#if currentSetting.hideLogo}}is-checked{{/if}}")
span {{_ 'hide-logo'}}
li.tableVisibilityMode-form
.title {{_ 'custom-login-logo-image-url'}}
.form-group
input.wekan-form-control#custom-login-logo-image-url(type="text", placeholder="" value="{{currentSetting.customLoginLogoImageUrl}}")
input.js-site-logo-upload(type="file" data-kind="login" accept="image/png,image/jpeg,image/gif,image/webp" aria-label="{{_ 'upload'}} {{_ 'custom-login-logo-image-url'}}")
li.tableVisibilityMode-form
.title {{_ 'custom-login-logo-link-url'}}
.form-group
input.wekan-form-control#custom-login-logo-link-url(type="text", placeholder="" value="{{currentSetting.customLoginLogoLinkUrl}}")
li.tableVisibilityMode-form
.title {{_ 'text-below-custom-login-logo'}}
.form-group
textarea#text-below-custom-login-logo.wekan-form-control(data-editor-submit=".js-visibility-logo-save")= currentSetting.textBelowCustomLoginLogo
li.tableVisibilityMode-form
.title {{_ 'login-background-color'}}
.form-group
input.wekan-form-control#login-background-color(type="text", placeholder="#1b365d" value="{{currentSetting.loginBackgroundColor}}")
li.tableVisibilityMode-form
.title {{_ 'custom-top-left-corner-logo-image-url'}}
.form-group
input.wekan-form-control#custom-top-left-corner-logo-image-url(type="text", placeholder="" value="{{currentSetting.customTopLeftCornerLogoImageUrl}}")
input.js-site-logo-upload(type="file" data-kind="header" accept="image/png,image/jpeg,image/gif,image/webp" aria-label="{{_ 'upload'}} {{_ 'custom-top-left-corner-logo-image-url'}}")
li.tableVisibilityMode-form
span.js-site-logo-upload-status(role="status" aria-live="polite")
li.tableVisibilityMode-form
.title {{_ 'custom-top-left-corner-logo-link-url'}}
.form-group
input.wekan-form-control#custom-top-left-corner-logo-link-url(type="text", placeholder="" value="{{currentSetting.customTopLeftCornerLogoLinkUrl}}")
li.tableVisibilityMode-form
.title {{_ 'custom-top-left-corner-logo-height'}}
.form-group
input.wekan-form-control#custom-top-left-corner-logo-height(type="text", placeholder="" value="{{currentSetting.customTopLeftCornerLogoHeight}}")
li
button.js-visibility-logo-save.primary {{_ 'save'}}
+themeColorPicker(scope="admin")
if isSiteAdmin
li.admin-pane-group-separator
hr
li
h2.admin-pane-group-title {{_ 'settings-group-logo'}}
li.tableVisibilityMode-form
//- One checkbox, like the All Boards group above and like Announcement's
//- "Active System-Wide Announcement": ticked = the logo is hidden. The
//- group's Save below writes it, as it wrote the Yes/No pair.
a.flex.js-toggle-hide-logo
.materialCheckBox#hide-logo(class="{{#if currentSetting.hideLogo}}is-checked{{/if}}")
span {{_ 'hide-logo'}}
li.tableVisibilityMode-form
.title {{_ 'custom-login-logo-image-url'}}
.form-group
input.wekan-form-control#custom-login-logo-image-url(type="text", placeholder="" value="{{currentSetting.customLoginLogoImageUrl}}")
input.js-site-logo-upload(type="file" data-kind="login" accept="image/png,image/jpeg,image/gif,image/webp" aria-label="{{_ 'upload'}} {{_ 'custom-login-logo-image-url'}}")
li.tableVisibilityMode-form
.title {{_ 'custom-login-logo-link-url'}}
.form-group
input.wekan-form-control#custom-login-logo-link-url(type="text", placeholder="" value="{{currentSetting.customLoginLogoLinkUrl}}")
li.tableVisibilityMode-form
.title {{_ 'text-below-custom-login-logo'}}
.form-group
textarea#text-below-custom-login-logo.wekan-form-control(data-editor-submit=".js-visibility-logo-save")= currentSetting.textBelowCustomLoginLogo
li.tableVisibilityMode-form
.title {{_ 'login-background-color'}}
.form-group
input.wekan-form-control#login-background-color(type="text", placeholder="#1b365d" value="{{currentSetting.loginBackgroundColor}}")
li.tableVisibilityMode-form
.title {{_ 'custom-top-left-corner-logo-image-url'}}
.form-group
input.wekan-form-control#custom-top-left-corner-logo-image-url(type="text", placeholder="" value="{{currentSetting.customTopLeftCornerLogoImageUrl}}")
input.js-site-logo-upload(type="file" data-kind="header" accept="image/png,image/jpeg,image/gif,image/webp" aria-label="{{_ 'upload'}} {{_ 'custom-top-left-corner-logo-image-url'}}")
li.tableVisibilityMode-form
span.js-site-logo-upload-status(role="status" aria-live="polite")
li.tableVisibilityMode-form
.title {{_ 'custom-top-left-corner-logo-link-url'}}
.form-group
input.wekan-form-control#custom-top-left-corner-logo-link-url(type="text", placeholder="" value="{{currentSetting.customTopLeftCornerLogoLinkUrl}}")
li.tableVisibilityMode-form
.title {{_ 'custom-top-left-corner-logo-height'}}
.form-group
input.wekan-form-control#custom-top-left-corner-logo-height(type="text", placeholder="" value="{{currentSetting.customTopLeftCornerLogoHeight}}")
li
button.js-visibility-logo-save.primary {{_ 'save'}}
template(name='announcementSettings')
ul#announcement-setting.setting-detail
+115 -4
View File
@@ -147,6 +147,15 @@ Template.setting.onCreated(function () {
this.layoutSetting = new ReactiveVar(false);
this.webhookSetting = new ReactiveVar(false);
this.sharedLabelsSetting = new ReactiveVar(false);
// 2026-11-19: what WeKan offers and who sees it, in one place - Features and
// Feature profiles split out of Visibility (now Appearance), and Security,
// Activities and notifications and Delete moved here from Admin Panel /
// Problems, where settings sat among the reports.
this.featuresSetting = new ReactiveVar(false);
this.featureProfilesSetting = new ReactiveVar(false);
this.privacySecuritySetting = new ReactiveVar(false);
this.activitiesSetting = new ReactiveVar(false);
this.deleteSetting = new ReactiveVar(false);
// The pane the URL asks for. `/settings/global-webhooks` opens Global
// Webhooks; the bare `/settings` opens the default, which the route resolved
// for us, so this is always a real pane id. Reactive, so following a link to
@@ -186,6 +195,11 @@ Template.setting.onDestroyed(function () {
const SETTINGS_PANE_VARS = {
'version-setting': 'versionSetting',
'tableVisibilityMode-setting': 'tableVisibilityModeSetting',
'features-setting': 'featuresSetting',
'feature-profiles-setting': 'featureProfilesSetting',
'privacy-security-setting': 'privacySecuritySetting',
'activities-setting': 'activitiesSetting',
'delete-setting': 'deleteSetting',
'announcement-setting': 'announcementSetting',
'accessibility-setting': 'accessibilitySetting',
'translation-setting': 'translationSetting',
@@ -214,10 +228,19 @@ function settingsMenu(user) {
const items = [
// First, and open by default - see Template.setting.onCreated.
{ id: 'version-setting', icon: 'fa-info-circle', labelKey: 'info', emoji: true },
// Labelled just 'Visibility' now. The pane id and the tableVisibilityMode
// key are unchanged, so the 141 translations of the pane's own contents are
// untouched; only the menu label points at the new key.
{ id: 'tableVisibilityMode-setting', icon: 'fa-eye', labelKey: 'visibility', emoji: true },
// Appearance (2026-11-19; it was Visibility): how this WeKan looks - what
// All Boards shows, dates, URLs, the product name, colours and logos. The
// pane id is unchanged, so an Organization admin's one pane (Change color)
// is still this one.
{ id: 'tableVisibilityMode-setting', icon: 'fa-paint-brush', labelKey: 'appearance', emoji: true },
// What this WeKan offers and who sees it: the optional features, then the
// profiles that hide some of them from chosen people.
{ id: 'features-setting', icon: 'fa-toggle-on', labelKey: 'features', emoji: true },
{ id: 'feature-profiles-setting', icon: 'fa-eye-slash', labelKey: 'feature-profiles', emoji: true },
// Moved from Admin Panel / Problems: settings, not reports.
{ id: 'privacy-security-setting', icon: 'fa-shield', labelKey: 'features-security', emoji: true },
{ id: 'activities-setting', icon: 'fa-bell', labelKey: 'activities-and-notifications', emoji: true },
{ id: 'delete-setting', icon: 'fa-trash', labelKey: 'delete', emoji: true },
{ id: 'announcement-setting', icon: 'fa-bullhorn', labelKey: 'admin-announcement', emoji: true },
{ id: 'accessibility-setting', icon: 'fa-universal-access', labelKey: 'accessibility', emoji: true },
// PWA is an acronym, not a translated string - a literal label, like the
@@ -245,6 +268,11 @@ function activeSettingId(inst) {
const panes = [
['versionSetting', 'version-setting'],
['tableVisibilityModeSetting', 'tableVisibilityMode-setting'],
['featuresSetting', 'features-setting'],
['featureProfilesSetting', 'feature-profiles-setting'],
['privacySecuritySetting', 'privacy-security-setting'],
['activitiesSetting', 'activities-setting'],
['deleteSetting', 'delete-setting'],
['announcementSetting', 'announcement-setting'],
['accessibilitySetting', 'accessibility-setting'],
['translationSetting', 'translation-setting'],
@@ -306,6 +334,26 @@ Template.setting.helpers({
const inst = Template.instance();
return inst.sharedLabelsSetting && inst.sharedLabelsSetting.get();
},
isFeaturesSetting() {
const inst = Template.instance();
return inst.featuresSetting && inst.featuresSetting.get();
},
isFeatureProfilesSetting() {
const inst = Template.instance();
return inst.featureProfilesSetting && inst.featureProfilesSetting.get();
},
isPrivacySecuritySetting() {
const inst = Template.instance();
return inst.privacySecuritySetting && inst.privacySecuritySetting.get();
},
isActivitiesSetting() {
const inst = Template.instance();
return inst.activitiesSetting && inst.activitiesSetting.get();
},
isDeleteSetting() {
const inst = Template.instance();
return inst.deleteSetting && inst.deleteSetting.get();
},
isLoading() {
const inst = Template.instance();
return inst.loading && inst.loading.get();
@@ -524,14 +572,43 @@ Template.setting.events({
// user, visible only to that user), so the site admin's page asks for them.
Template.tableVisibilityModeSettings.onCreated(function () {
this.featurePilotUsernames = new ReactiveVar('');
// #6837: the feature profiles, with the names of what they apply to. The
// page edits these rows; Save sends them all (saveFeatureProfiles).
this.featureProfiles = new ReactiveVar([]);
if (tenantAdmin.isSiteAdmin(ReactiveCache.getCurrentUser())) {
Meteor.callAsync('getFeaturePilotUsernames')
.then(names => this.featurePilotUsernames.set(names.join(', ')))
.catch(() => {});
Meteor.callAsync('getFeatureProfiles')
.then(profiles => this.featureProfiles.set(profiles.map(p => ({ ...p,
teams: p.teams.join('\n'), orgs: p.orgs.join('\n'), usernames: p.usernames.join(', ') }))))
.catch(() => {});
}
});
// #6837: the profile rows as the page shows them now, edits included.
function readFeatureProfiles(instance) {
return instance.$('.js-feature-profile').toArray().map(row => {
const $row = $(row);
return {
_id: row.dataset.profileId || undefined,
name: $row.find('.js-feature-profile-name').val() || '',
hidden: $row.find('.js-feature-profile-hide').toArray()
.filter(a => $(a).find('.materialCheckBox').hasClass('is-checked')).map(a => a.dataset.feature),
usernames: $row.find('.js-feature-profile-users').val() || '',
teams: $row.find('.js-feature-profile-teams').val() || '',
orgs: $row.find('.js-feature-profile-orgs').val() || '',
};
});
}
Template.tableVisibilityModeSettings.helpers({
// Which of the three panes this is: 'appearance' (the default), 'features'
// or 'profiles' (Template.setting renders it once per pane).
isPart(part) {
const data = Template.currentData() || {};
return (data.part || 'appearance') === part;
},
featureRows() {
return instanceFeatures.featureRows(ReactiveCache.getCurrentSetting());
},
@@ -551,6 +628,13 @@ Template.tableVisibilityModeSettings.helpers({
featurePilotUsernames() {
return Template.instance().featurePilotUsernames.get();
},
featureProfileRows() {
return Template.instance().featureProfiles.get().map(profile => ({
...profile,
rows: instanceFeatures.FEATURES.map(feature => ({ key: feature.key, labelKey: feature.labelKey,
hidden: (profile.hidden || []).includes(feature.key) })),
}));
},
isGlobalDateFormat(format) {
return (ReactiveCache.getCurrentSetting()?.globalDateFormat || 'YYYY-MM-DD') === format;
},
@@ -692,6 +776,33 @@ Template.tableVisibilityModeSettings.events({
status.text(error.reason || error.message);
}
},
// #6837: add a profile, remove one, and save them all.
'click button.js-feature-profile-add'(event, instance) {
event.preventDefault();
instance.featureProfiles.set([...readFeatureProfiles(instance),
{ name: '', hidden: [], usernames: '', teams: '', orgs: '' }]);
},
'click button.js-feature-profile-remove'(event, instance) {
event.preventDefault();
const index = instance.$('.js-feature-profile').index($(event.currentTarget).closest('.js-feature-profile'));
instance.featureProfiles.set(readFeatureProfiles(instance).filter((p, i) => i !== index));
},
async 'click button.js-feature-profiles-save'(event, instance) {
event.preventDefault();
const status = instance.$('.js-feature-profiles-status');
try {
const result = await Meteor.callAsync('saveFeatureProfiles', readFeatureProfiles(instance)
.map(({ _id, ...rest }) => (_id ? { _id, ...rest } : rest)));
const profiles = await Meteor.callAsync('getFeatureProfiles');
instance.featureProfiles.set(profiles.map(p => ({ ...p,
teams: p.teams.join('\n'), orgs: p.orgs.join('\n'), usernames: p.usernames.join(', ') })));
const unknown = [...result.unknown.usernames, ...result.unknown.teams, ...result.unknown.orgs];
status.text(unknown.length ? `${TAPi18n.__('feature-profile-unknown')} ${unknown.join(', ')}` : TAPi18n.__('feature-saved'));
} catch (error) {
status.text(error.reason || error.error || error.message);
}
},
async 'click button.js-visibility-features-save'(event, instance) {
event.preventDefault();
const states = {};
+8 -2
View File
@@ -463,7 +463,13 @@ body.swimlane-resizing-active * {
/* #2805: one shared list header row for all swimlanes (Board Settings /
Swimlane). The other swimlanes do not repeat the first swimlane's list
headers; those stay at the top through the same sticky rule as Sticky list
headers (#3847, lists/list.css), which the setting turns on. */
headers (#3847, lists/list.css), which the setting turns on.
!important: the desktop list header layout sets `display: block !important`
(lists/list.css `.list:not(.list-collapsed):not(.mobile-view) .list-header`,
boardHeader.css `.desktop-mode .list-header`), and a plain `display: none`
loses to any !important one, so every swimlane kept its headers. Between
!important declarations specificity decides, and this selector (0,5,0)
outranks those (0,4,0 at most). tests/sharedListRow6902.test.cjs. */
.board-canvas.shared-list-headers .js-swimlane:not(.is-first-swimlane) .list-header {
display: none;
display: none !important;
}
+6
View File
@@ -13,6 +13,12 @@ template(name="headerUserBar")
= currentUser.username
template(name="memberMenuPopup")
//- #6837: a feature profile hides features on purpose, and says so, so a
hidden feature is never taken for a missing one (models/lib/featureProfiles.js).
with featureProfileNotice
p.feature-profile-notice.quiet(role="note")
i.fa.fa-eye-slash(aria-hidden="true")
| {{_ 'feature-profile-notice' name=name count=hiddenCount}}
ul.pop-over-list
with currentUser
//- #6732: at the top - Show My / Show Board Dependencies, Import, Export.
+57
View File
@@ -0,0 +1,57 @@
// #6924: the card shortcuts open ONLY their popup. `d` (Due date), Shift+M
// (Move card) and Shift+C (Copy card) on a hovered or selected minicard used
// to open the card first, and Shift+M / Shift+C went through the card's
// hamburger menu too - three things for one key. Now the popup opens by
// itself, next to the minicard, as a click on a minicard's due date or label
// opens only its popup; on an opened card, Move / Copy open next to the card's
// hamburger without showing the menu first.
//
// The popup is opened directly, so these are the rules a click would meet.
// Each one is the condition the opened card renders that control under, and
// tests/cardShortcutPopup.test.cjs ties every rule to that template:
// due cardDetails.jade: `if currentBoard.allowsDueDate`, then the date
// badge (`if canModifyCard`) when the card has a due date, or the add
// `+` (`if canModifyCard` / `unless currentUser.isWorker`) when not;
// move cardDetailsActionsPopup: `if cardMenuWrites` / `if currentUser.isBoardAdmin`;
// copy cardDetailsActionsPopup: `if cardMenuWrites` / `unless currentUser.isWorker`.
// cardMenuWrites (cardDetails.js) is: may modify the card, or is a member who
// is neither read-only nor read-assigned-only.
//
// Pure, no Meteor imports, so the test drives it without a browser.
export const CARD_SHORTCUT_POPUPS = Object.freeze({
due: 'editCardDueDate',
move: 'moveCard',
copy: 'copyCard',
});
// facts: { canModifyCard, isBoardAdmin, isWorker, isReadOnly,
// isReadAssignedOnly, allowsDueDate, hasDue } - booleans.
// Returns the popup name to open, or null when a click could not open it.
export function cardShortcutPopup(action, facts = {}) {
const f = facts || {};
const cardMenuWrites = Boolean(f.canModifyCard) || !(f.isReadOnly || f.isReadAssignedOnly);
switch (action) {
case 'due':
if (f.allowsDueDate === false || !f.canModifyCard) return null;
if (!f.hasDue && f.isWorker) return null;
return CARD_SHORTCUT_POPUPS.due;
case 'move':
return cardMenuWrites && f.isBoardAdmin ? CARD_SHORTCUT_POPUPS.move : null;
case 'copy':
return cardMenuWrites && !f.isWorker ? CARD_SHORTCUT_POPUPS.copy : null;
default:
return null;
}
}
const SAFE_ID = /^[A-Za-z0-9_-]+$/;
// The minicard element of a card, to anchor its popup: the hovered one when it
// is that card (a card can be on the board more than once), else the first.
// null for an id that is not a plain id, so it never reaches a selector.
export function findMinicard(root, cardId, hovered = null) {
if (!root || typeof cardId !== 'string' || !SAFE_ID.test(cardId)) return null;
if (hovered && hovered.getAttribute && hovered.getAttribute('data-card-id') === cardId) return hovered;
return root.querySelector(`.js-minicard[data-card-id="${cardId}"]`) || null;
}
@@ -265,9 +265,6 @@ export class BoardSwimlaneListDialog {
const lanes = this.swimlanes();
if (!lanes.some(lane => lane._id === this.selectedSwimlaneId.get())) this.setFirstSwimlaneId();
if (!this.lists().some(list => list._id === this.selectedListId.get())) this.setFirstListId();
if (this.selectedCardId && !this.cards().some(card => card._id === this.selectedCardId.get())) {
this.selectedCardId.set('');
}
this.loading.set(false);
},
onStop: error => {
+30 -1
View File
@@ -10,6 +10,33 @@ export class BoardSwimlaneListCardDialog extends BoardSwimlaneListDialog {
constructor(tpl, callbacks = {}) {
super(tpl, callbacks);
this.selectedCardId = new ReactiveVar(this.cardOption.cardId || '');
this.cardsLoading = new ReactiveVar(true);
// #6917: the destination's cards come from a picker-owned subscription,
// not from the `board` publication, which ships no cards at all for a
// board that loads lazily (Card loading = lazy, or 'auto' above the
// threshold). Subscribing inside the template's autorun stops the previous
// list's subscription when another board, swimlane or list is chosen, and
// the last one when the popup closes.
this.tpl.autorun?.(() => {
const boardId = this.selectedBoardId.get();
const listId = this.selectedListId.get();
const swimlaneId = this.selectedSwimlaneId.get();
const request = (this._cardsRequest = (this._cardsRequest || 0) + 1);
this.cardsLoading.set(true);
if (!boardId || !listId || !swimlaneId) return;
this.tpl.subscribe('destinationCards', boardId, listId, swimlaneId, {
onReady: () => {
if (this._disposed || request !== this._cardsRequest) return;
// A remembered card is checked here, once this list's cards are
// there - the board being ready says nothing about its cards.
const cardId = this.selectedCardId.get();
if (cardId && !this.cards().some(card => card._id === cardId)) {
this.selectedCardId.set('');
}
this.cardsLoading.set(false);
},
});
});
}
getDefaultOption() {
@@ -37,7 +64,9 @@ export class BoardSwimlaneListCardDialog extends BoardSwimlaneListDialog {
});
const swimlaneId = this.selectedSwimlaneId.get();
if (list && swimlaneId) {
return list.cards(swimlaneId).sort((a, b) => a.sort - b.sort);
// Unfiltered: the open board's Filter describes that board, and must not
// empty the dropdown of the destination (#6917).
return list.cardsUnfiltered(swimlaneId).sort((a, b) => a.sort - b.sort);
} else {
return [];
}
+10 -1
View File
@@ -11,7 +11,8 @@ const { isBoardViewAvailable, isFeatureAvailable } = require('/models/lib/instan
// calls this, and every list's card loop reads boardView(): with the whole user
// document here, a card open (a user write) re-ran every list and Blaze then
// re-evaluated every minicard.
const PREVIEW_USER_FIELDS = ['featurePreview', 'isAdmin'];
// #6837: and the three that pick the user's feature profile.
const PREVIEW_USER_FIELDS = ['featurePreview', 'isAdmin', 'featureProfileId', 'teams', 'orgs'];
export function allowBoardView(view) {
return isBoardViewAvailable(ReactiveCache.getCurrentSetting(), currentUserWith(PREVIEW_USER_FIELDS), view);
@@ -25,3 +26,11 @@ export function allowFeature(key) {
// {{#if allowFeature 'board-summary'}} in a template.
Template.registerHelper('allowFeature', key => allowFeature(key));
// #6837: the profile that hides features for the signed-in user, so the
// interface can say so - a hidden feature must never look like a missing one.
export function featureProfileNotice() {
return require('/models/lib/featureProfiles').featureProfileNotice(
ReactiveCache.getCurrentSetting(), currentUserWith(PREVIEW_USER_FIELDS));
}
Template.registerHelper('featureProfileNotice', () => featureProfileNotice());
+54 -29
View File
@@ -10,7 +10,8 @@ import { Utils } from '/client/lib/utils';
import { newHistoryRequestId, runKeystroke } from '/client/lib/historyKeyRequest';
import { historyRequestStorage, refreshPendingHistoryRequest } from '/client/lib/historyKeyRecovery';
import { findDueDateControl } from '/client/lib/dueDateHotkey';
import { cardMenuStep } from '/client/lib/cardMenuHotkey';
import { findCardMenuOpener } from '/client/lib/cardMenuHotkey';
import { cardShortcutPopup, findMinicard } from '/client/lib/cardShortcutPopup';
// Late-bind Sidebar to avoid circular dependency (sidebar.js needs its template first)
let _Sidebar;
@@ -424,39 +425,67 @@ export function openDueDateEditorOfOpenedCard() {
return true;
}
// #6755: with no card opened, `d` on a hovered or selected minicard - the
// card every other card shortcut here acts on - opens that card and then
// its Due date editor, rather than doing nothing until the card is opened.
const minicardId = Session.get('selectedCard') || getHoveredCardId();
const minicard = minicardId && ReactiveCache.getCard(minicardId);
if (!minicard || !Utils.canModifyCard(minicard)) return false;
Utils.goCardId(minicardId);
setTimeout(() => clickDueDateControlWhenRendered(minicardId), 0);
return true;
// card every other card shortcut here acts on - opens its Due date editor.
// #6924: only the editor, next to the minicard, as a click on the
// minicard's due date does; the card itself stays closed.
return openCardShortcutPopupAtMinicard('due');
}
hotkeys('d, shift+d', (event) => {
event.preventDefault();
openDueDateEditorOfOpenedCard();
});
// #6904: Shift+M opens Move card and Shift+C opens Copy card, through the
// opened card's own hamburger menu (client/lib/cardMenuHotkey.js), so the
// menu's permissions decide whether there is anything to open. With no card
// opened, the hovered or selected minicard is opened first, as for `d`.
// Shift keeps them apart from `m` (assign yourself) and `c` (archive).
function runCardMenuActionWhenRendered(cardId, action) {
// #6904: Shift+M opens Move card and Shift+C opens Copy card. Shift keeps them
// apart from `m` (assign yourself) and `c` (archive).
// #6924: each opens ONLY its popup. The popup is opened directly, so
// cardShortcutPopup (client/lib/cardShortcutPopup.js) applies the rules the
// controls a click would use are rendered under - the hamburger menu's Move
// card / Copy card items, the due date badge and its `+` - and without them
// nothing opens.
function cardShortcutFacts(card) {
const user = ReactiveCache.getCurrentUser();
const board = ReactiveCache.getBoard(card.boardId);
return {
canModifyCard: Utils.canModifyCard(card),
isBoardAdmin: Boolean(user && user.isBoardAdmin && user.isBoardAdmin()),
isWorker: Boolean(user && user.isWorker && user.isWorker()),
isReadOnly: Boolean(user && user.isReadOnly && user.isReadOnly()),
isReadAssignedOnly: Boolean(user && user.isReadAssignedOnly && user.isReadAssignedOnly()),
allowsDueDate: !board || board.allowsDueDate !== false,
hasDue: Boolean(card.getDue && card.getDue()),
};
}
// Opens the popup next to `anchor`, with the card as its data context - as
// the minicard's own menu and date badges open theirs (minicard.js,
// cardDate.js openDateEditor).
function openCardShortcutPopup(action, card, anchor) {
const name = cardShortcutPopup(action, cardShortcutFacts(card));
if (!name || !anchor) return false;
Popup.open(name).call(card, { currentTarget: anchor, target: anchor, preventDefault() {} });
return true;
}
// With no card opened: the hovered or selected minicard, the card every other
// card shortcut here acts on. The card is not opened.
function openCardShortcutPopupAtMinicard(action) {
const minicardId = Session.get('selectedCard') || getHoveredCardId();
const minicard = minicardId && ReactiveCache.getCard(minicardId);
if (!minicard) return false;
const anchor = findMinicard(document, minicardId, $('.js-minicard:hover').get(0));
return openCardShortcutPopup(action, minicard, anchor);
}
// #6840: an opened card's details render a moment after the route names it,
// so the popup waits for the card's hamburger to anchor to, and gives up
// after 3 seconds.
function openCardShortcutPopupWhenRendered(cardId, action) {
const started = Date.now();
let menuOpened = false;
const step = () => {
if (Utils.getCurrentCardId() !== cardId) return;
const result = cardMenuStep(document, {
cardId, action, menuOpened, dataOf: element => Blaze.getData(element),
});
if (result === 'clicked-item') return;
if (result === 'no-item') {
Popup.close();
const card = ReactiveCache.getCard(cardId);
const anchor = card && findCardMenuOpener(document, { cardId, dataOf: element => Blaze.getData(element) });
if (anchor) {
openCardShortcutPopup(action, card, anchor);
return;
}
if (result === 'opened-menu') menuOpened = true;
if (Date.now() - started < 3000) setTimeout(step, 50);
};
step();
@@ -466,14 +495,10 @@ export function openCardMenuActionOfOpenedCard(action) {
const cardId = Utils.getCurrentCardId();
if (cardId) {
if (!ReactiveCache.getCard(cardId)) return false;
runCardMenuActionWhenRendered(cardId, action);
openCardShortcutPopupWhenRendered(cardId, action);
return true;
}
const minicardId = Session.get('selectedCard') || getHoveredCardId();
if (!minicardId || !ReactiveCache.getCard(minicardId)) return false;
Utils.goCardId(minicardId);
setTimeout(() => runCardMenuActionWhenRendered(minicardId, action), 0);
return true;
return openCardShortcutPopupAtMinicard(action);
}
hotkeys('shift+m', (event) => {
event.preventDefault();
+5 -2
View File
@@ -884,9 +884,12 @@ export const Utils = {
// never chosen. The three states matter — see showDragHandles() below.
dragHandlesPreference() {
// #6745: read by every minicard - one field, not the whole user document.
const currentUser = currentUserWith(['profile.showDesktopDragHandles']);
// #6919: the profile's own value when the client has the profile, else the
// one userDesktopDragHandles publishes under a top-level field of its own.
const currentUser = currentUserWith(['profile.showDesktopDragHandles', 'desktopDragHandlesPreference']);
const fromProfile = currentUser && (currentUser.profile || {}).showDesktopDragHandles;
const stored = currentUser
? (currentUser.profile || {}).showDesktopDragHandles
? (fromProfile !== undefined ? fromProfile : currentUser.desktopDragHandlesPreference)
// Not logged in: the same three states, kept in localStorage. A MISSING
// key is "never chosen"; the string 'false' is a deliberate "off".
: window.localStorage.getItem('showDesktopDragHandles');
+13 -1
View File
@@ -23,7 +23,16 @@ import {
resolvePaneId,
adminPath,
adminRoutePath,
movedPanePath,
} from '/models/lib/adminUrls';
// A pane that moved (models/lib/adminUrls.js MOVED_PANES): its old address
// redirects to the new one, so a bookmark keeps working. A trigger redirects
// with the `redirect` it is handed, never FlowRouter.go() (see below).
const redirectMovedPane = page => (context, redirect) => {
const to = movedPanePath(page, (context.params || {}).pane);
if (to) redirect(to);
};
// The All Boards page's URLs: /allboards/starred, /allboards/templates,
// /allboards/remaining, /allboards/workspaces/<name>/<sub-name>.
// docs/Features/All-Boards/URLs.md
@@ -843,6 +852,7 @@ FlowRouter.route('/import/:source', {
FlowRouter.route(adminRoutePath('settings'), {
name: 'setting',
triggersEnter: [
redirectMovedPane('settings'),
ensureSignedInUnlessSandstorm,
() => {
Session.set('currentBoard', null);
@@ -887,7 +897,8 @@ Object.keys(ADMIN_PAGES).forEach(page => {
// unknown one falls back to the default rather than 404ing a bookmark.
FlowRouter.route(`${cfg.legacyBase}/:pane`, {
triggersEnter: [
(context, redirect) => redirect(adminPath(page, (context.params || {}).pane)),
(context, redirect) => redirect(movedPanePath(page, (context.params || {}).pane)
|| adminPath(page, (context.params || {}).pane)),
],
action() {},
});
@@ -953,6 +964,7 @@ FlowRouter.route(adminRoutePath('people'), {
FlowRouter.route(adminRoutePath('problems'), {
name: 'problems',
triggersEnter: [
redirectMovedPane('problems'),
ensureSignedInUnlessSandstorm,
() => {
Session.set('currentBoard', null);
+1 -1
View File
@@ -1,6 +1,6 @@
# Optional APIs: Trello, Jira, GitHub and Gitea compatible
Admin Panel → Settings → Visibility → **Optional APIs** turns on REST APIs in
Admin Panel → Settings → Features → **Optional APIs** turns on REST APIs in
the shape of other trackers' APIs (#4930). An app or script written for Trello,
Jira, GitHub or Gitea can then use this WeKan as its backend: what it saves is
stored in WeKan's database, on WeKan boards, and is seen in WeKan like any
@@ -114,7 +114,7 @@ may mark an abandoned redo branch `superseded`.
The existing filesystem-integrity inventory covers attachments and avatars. The
same paced audit also covers registered logs and verified recovery generations.
Missing files, changed sizes, invalid signed baselines and changed checksums are
reported in Admin Panel → Problems → Security. Intentional application deletion
reported in Admin Panel → Problems → Security Report. Intentional application deletion
removes its inventory entry as part of the authorized operation and is not called
tampering.
+2 -2
View File
@@ -364,7 +364,7 @@ never quietly narrowed.
#### D.9 The singletons (problem 6)
Per-tenant branding reuses the fields Admin Panel / Settings / Visibility already
Per-tenant branding reuses the fields Admin Panel / Settings / Appearance already
has: the org document carries an `org`-prefixed copy of each, and a non-empty one
replaces the instance value for that tenant's requests
(`tenantBranding()`), so no rendering code changed — the client reads the same
@@ -382,7 +382,7 @@ host.
| `orgLegalNotice` | the legal notice URL |
**The site theme** is the one branding field an Organization's own admin sets from
the Admin Panel rather than from the org row: Admin Panel / Settings / Visibility /
the Admin Panel rather than from the org row: Admin Panel / Settings / Appearance /
**Change color**, the same shared picker as Board Settings and Member Settings
([Change color](../../Features/General/Theme/Change-Color.md)). The site admin's pane says under the title that
their colour is the one every Organization without one of its own inherits; an
+19 -4
View File
@@ -36,7 +36,12 @@ The bare `/admin/settings` still resolves; it *redirects* to
| URL | Pane | Pane id |
| --- | --- | --- |
| `/admin/settings/version` | Version | `version-setting` |
| `/admin/settings/visibility` | Visibility | `tableVisibilityMode-setting` |
| `/admin/settings/appearance` | Appearance | `tableVisibilityMode-setting` |
| `/admin/settings/features` | Features | `features-setting` |
| `/admin/settings/feature-profiles` | Feature profiles | `feature-profiles-setting` |
| `/admin/settings/security` | Security | `privacy-security-setting` |
| `/admin/settings/activities` | Activities and notifications | `activities-setting` |
| `/admin/settings/delete` | Delete | `delete-setting` |
| `/admin/settings/announcement` | Announcement | `announcement-setting` |
| `/admin/settings/accessibility` | Accessibility | `accessibility-setting` |
| `/admin/settings/translation` | Translation | `translation-setting` |
@@ -75,9 +80,6 @@ OAuth providers and Passwordless login each have their own menu entry.
| URL | Pane | Pane id |
| --- | --- | --- |
| `/admin/problems/summary` | Summary | `report-summary` |
| `/admin/problems/security` | Security | `features-security` |
| `/admin/problems/delete` | Delete | `features-delete` |
| `/admin/problems/notifications` | Notifications | `features-notifications` |
| `/admin/problems/backup` | Backup (status and history; settings stay in Attachments / Backup) | `features-backup` |
| `/admin/problems/security-report` | Security Report | `report-security` |
| `/admin/problems/impersonation` | Impersonation Report | `report-impersonation` |
@@ -179,6 +181,19 @@ They used to hand the pane over in a `Session` value the page consumed once.
Every pane has an address now, so they redirect to it: the pane ends up in the
URL, where it can be linked, bookmarked and gone back to.
### Panes that moved
A pane that moved keeps its old address as a redirect, decided by `MOVED_PANES`
in `models/lib/adminUrls.js` (`movedPanePath`) and applied by the routes before
anything renders - both on the new form and on the old two-segment form:
| Old URL | Redirects to | Since |
| --- | --- | --- |
| `/admin/settings/visibility` | `/admin/settings/appearance` | 2026-11-19 |
| `/admin/problems/security` | `/admin/settings/security` | 2026-11-19 |
| `/admin/problems/delete` | `/admin/settings/delete` | 2026-11-19 |
| `/admin/problems/notifications` | `/admin/settings/activities` | 2026-11-19 |
## How a page opens the pane
The route resolves the slug and puts the **pane id** in a Session value —
+57 -23
View File
@@ -5,11 +5,25 @@ your member menu (top right). Site administrators have instance-wide access;
Organization administrators have access only to their permitted scope.
**The directory you are in mirrors the menu.** A menu path is a docs path:
Admin Panel / Settings / Visibility is
[`Settings/Visibility.md`](Settings/Visibility.md), Admin Panel / People / Teams is
Admin Panel / Settings / Appearance is
[`Settings/Appearance.md`](Settings/Appearance.md), Admin Panel / People / Teams is
[`People/Teams.md`](People/Teams.md), and so on. The tab bar has four sections, and
each has its own left menu — the shared design behind both is
[Left Menu](../All-Boards/Left-Menu.md).
[Left Menu](../All-Boards/Left-Menu.md). Every pane has its own address,
`/admin/<tab>/<pane>` ([Admin Panel URLs](Admin-Panel-URLs.md)).
**One question per tab:**
| Tab | Answers |
| --- | --- |
| [Settings](Settings/README.md) | What does this WeKan offer, how does it look, and how does it behave? |
| [People](People/README.md) | Who may sign in, who do they belong to, and what may they do? |
| [Attachments](Attachments/README.md) | Where are files kept, how big may they be, and are they backed up? |
| [Problems](Problems/README.md) | What is going wrong, what is running, and what happened? |
Which setting decides whether somebody sees or may use something - the instance,
a feature profile, the board, a role - is explained in one place:
[Who sees and can do what](Who-Sees-What.md).
## Settings
@@ -19,12 +33,18 @@ running. [Section index](Settings/README.md).
| Menu path | Page |
| --- | --- |
| Admin Panel / Settings / Version | [Version.md](Settings/Version.md) |
| Admin Panel / Settings / Visibility | [Visibility.md](Settings/Visibility.md) |
| Admin Panel / Settings / Appearance | [Appearance.md](Settings/Appearance.md) |
| Admin Panel / Settings / Features | [Features.md](Settings/Features.md) |
| Admin Panel / Settings / Feature profiles | [Feature-Profiles.md](Settings/Feature-Profiles.md) |
| Admin Panel / Settings / Security | [Security.md](Settings/Security.md) |
| Admin Panel / Settings / Activities and notifications | [Activities-and-Notifications.md](Settings/Activities-and-Notifications.md) |
| Admin Panel / Settings / Delete | [Delete.md](Settings/Delete.md) |
| Admin Panel / Settings / Announcement | [Announcement.md](Settings/Announcement.md) |
| Admin Panel / Settings / Accessibility | [Accessibility.md](Settings/Accessibility.md) |
| Admin Panel / Settings / Translation | [Translation.md](Settings/Translation.md) |
| Admin Panel / Settings / PWA | [PWA.md](Settings/PWA.md) |
| Admin Panel / Settings / Global Webhooks | [Global-Webhooks.md](Settings/Global-Webhooks.md) |
| Admin Panel / Settings / Shared labels | [Shared-Labels.md](Settings/Shared-Labels.md) |
## People
@@ -33,7 +53,6 @@ Who may sign in, who they belong to, and what they may do.
| Menu path | Page |
| --- | --- |
| Admin Panel / People / Login | [Login.md](People/Login.md) |
| Admin Panel / People / E-mail | [E-mail.md](People/E-mail.md) |
| Admin Panel / People / Notifications | [Notifications.md](People/Notifications.md) |
| Admin Panel / People / Domains | [Domains.md](People/Domains.md) |
@@ -41,8 +60,14 @@ Who may sign in, who they belong to, and what they may do.
| Admin Panel / People / Teams | [Teams.md](People/Teams.md) |
| Admin Panel / People / People | [People.md](People/People.md) |
| Admin Panel / People / Locked Users | [Locked-Users.md](People/Locked-Users.md) |
| Admin Panel / People / Audit log | [Audit-Log.md](People/Audit-Log.md) |
| Admin Panel / People / Roles | [Roles.md](People/Roles.md) |
| Admin Panel / People / Shared templates | [Shared-Templates.md](People/Shared-Templates.md) |
| Admin Panel / People / Login | [Login.md](People/Login.md) |
| Admin Panel / People / SAML, LDAP, OAuth2, CAS, Header login, OAuth login providers, Passwordless login | [Login.md](People/Login.md#provider-settings) |
The People, Teams and Organizations tables also show the
[feature profile](Settings/Feature-Profiles.md) that applies.
## Attachments
@@ -55,10 +80,11 @@ in menu order, starting with **Backup**, which is also the pane that opens.
Instance health: what is broken, what is running, and the paginated report tables.
[Section index](Problems/README.md).
The left menu is two named groups. **Settings** — Security and Notifications, the
two panes that came from the removed Features tab. **Reports** — Security Report,
Impersonation Report, Performance, Speed, Tests, CPU usage, Broken Cards, Files,
Rules, Boards, Cards and Recovery. Every report is one shared
**Summary** first, then **Backup** (did the backup work), then the **Reports**
group: Security Report, Impersonation Report, Password length, Performance, Speed,
Tests, CPU usage, Memory usage, Disk usage, Instrumentation, Broken Cards, Files
Report, Rules Report, Boards Report, Cards Report, Recovery, Offices, API,
Database problems, Filesystem integrity and Email. Every report is one shared
[table page](../General/Table.md): a search box, a total, `page X / N` and
prev/next.
@@ -69,20 +95,28 @@ Auth) and SMTP are handled by Sandstorm itself: you add and remove users there.
is no longer a **Sandstorm** pane in Attachments — see
[Attachments](Attachments/README.md#sandstorm--removed-from-the-menu).
## Two panes that are gone
## Panes that moved or are gone
- **Features** — removed. Performance, Security and Notifications are panes of
Admin Panel / Problems now.
- **Accounts** — removed. Its three settings live with what they are about: Allow
e-mail change in [People / E-mail](People/E-mail.md), Username change and Self
delete user account in [People / Login](People/Login.md).
When following an older link or bookmark - every old address redirects:
Renames to know when following an older link: **Layout** is
[PWA](Settings/PWA.md) — its branding and All Boards settings moved to
[Visibility](Settings/Visibility.md); **Boards visibility** is
[Visibility](Settings/Visibility.md); **Registration** is
[People / Login](People/Login.md); **Info** is
[Settings / Version](Settings/Version.md).
- **Settings / Visibility** (2026-11-19) is [Appearance](Settings/Appearance.md);
its Features group is [Features](Settings/Features.md) and its feature profiles
are [Feature profiles](Settings/Feature-Profiles.md).
- **Problems / Security, Delete and Notifications** (2026-11-19) are
[Settings / Security](Settings/Security.md),
[Settings / Delete](Settings/Delete.md) and
[Settings / Activities and notifications](Settings/Activities-and-Notifications.md):
they are settings, not reports.
- **Features** tab — removed (2026-07); its panes went to Problems, and from there
to Settings as above. Performance is still a Problems report.
- **Accounts** tab — removed. Its three settings live with what they are about:
Allow e-mail change in [People / E-mail](People/E-mail.md), Username change and
Self delete user account in [People / Login](People/Login.md).
- **Layout** is [PWA](Settings/PWA.md) — its branding and All Boards settings moved
to [Appearance](Settings/Appearance.md). **Boards visibility** is
[Appearance](Settings/Appearance.md). **Registration** is
[People / Login](People/Login.md). **Info** is
[Settings / Version](Settings/Version.md).
## Related
@@ -95,5 +129,5 @@ Renames to know when following an older link: **Layout** is
## Implementation validation
[Validation report](Validation.md): all 48 panes, backup fixes, test evidence
and external-service verification limits.
[Validation report](Validation.md): the panes, backup fixes, test evidence and
external-service verification limits.
@@ -48,7 +48,7 @@ branding and its own administrators. It is off unless the server is started with
corner logo, the custom help link and the legal notice URL. Each one that is set
replaces the instance value on this Organization's domains; each one left empty
keeps the instance value. The **theme colour** is set in
[Settings / Visibility / Change color](../Settings/Visibility.md) instead, by that
[Settings / Appearance / Change color](../Settings/Appearance.md#change-color) instead, by that
Organization's own admin.
Deactivating an Organization takes its domains off the air without losing any of this.
@@ -0,0 +1,36 @@
# Admin Panel / Problems / Boards Report
Every board on the instance, with its visibility, members, organizations and
teams. Address: `/admin/problems/boards`. Site administrators only, and over
the whole instance, not only the boards the administrator is a member of.
## The table
The shared [table page](../../General/Table.md), 10 rows a page, in the boards'
default sort order, fetched one page at a time from the server
(`boardsReport` publication, `getBoardsReportCount` method,
`server/publications/boards.js`):
| Column | Holds |
| --- | --- |
| Title | shortened to 30 characters |
| Id | the board id |
| Permission | `public`, `instance` or `private` |
| Archived? | Yes or No |
| Members | user names of the active members; a removed member is not listed ([#5122](https://github.com/wekan/wekan/issues/5122)) |
| Organizations | the organizations the board is shared with |
| Teams | the teams the board is shared with |
## Search and filter
- The search box applies when Enter is pressed and matches the board title,
case-insensitively.
- **Permission** - All, Public, Instance or Private - narrows the list to boards
of that visibility and starts again from page 1.
The pane is read-only.
## Related
- [Organizations](../People/Organizations.md) and [Teams](../People/Teams.md)
- [Cards Report](Cards-Report.md)
@@ -0,0 +1,36 @@
# Admin Panel / Problems / Broken Cards
Cards that cannot be shown on a board as they are. Address:
`/admin/problems/broken-cards`. Site administrators only, over every board of
the instance, whether or not the administrator is a member.
## What counts as broken
A card that has no board, no swimlane or no list (the field is missing or
empty), or whose type is not one of the card types WeKan knows
(`BROKEN_CARDS_SELECTOR` in `server/publications/cards.js`).
## The table
The shared [table page](../../General/Table.md), 10 rows a page, sorted by
board and then newest first, fetched one page at a time from the server
(`brokenCardsReport` publication, `getBrokenCardsReportCount` method):
| Column | Holds |
| --- | --- |
| Card Title | shortened to 30 characters |
| Id | the card id |
| Board, Swimlane, List | the titles of those that exist; an empty cell is the part that is missing |
| Type | the card's type |
| Created at | when the card was created |
The search box applies when Enter is pressed and matches the card title,
case-insensitively.
## Repairing
This pane only lists. The repair is on [Summary](Summary.md): the
**Broken cards** problem there has a **Repair broken cards** button, which runs
the repair over every board and says how many cards it fixed and how many have
no board at all and cannot be placed anywhere. Opening a board also repairs its
own cards ([Repairs.md](Repairs.md)).
@@ -0,0 +1,30 @@
# Admin Panel / Problems / Cards Report
Every card on the instance, with where it is and who is on it. Address:
`/admin/problems/cards`. Site administrators only, over every board, whether or
not the administrator is a member.
## The table
The shared [table page](../../General/Table.md), 10 rows a page, sorted by
board and then newest first, fetched one page at a time from the server
(`cardsReport` publication, `getCardsReportCount` method,
`server/publications/cards.js`). Only the columns below are sent, not whole
card documents:
| Column | Holds |
| --- | --- |
| Card Title | shortened to 30 characters |
| Board, Swimlane, List | the titles of each |
| Members | user names of the card's members |
| Assignees | user names of the card's assignees |
The search box applies when Enter is pressed and matches the card title,
case-insensitively. The total is counted once when the pane opens or the search
changes, not on every page. The pane is read-only.
## Related
- [Broken Cards](Broken-Cards.md) - the cards that are missing a board, swimlane
or list.
- [Boards Report](Boards-Report.md)
@@ -0,0 +1,62 @@
# Admin Panel / Problems / Database problems
What the database said, read for the administrator: which database said it,
what it means, and what to do. Address: `/admin/problems/database`. Site
administrators only.
## Where the rows come from
The `database` stream of the `eventlog` collection, written by
`server/lib/databaseProblems.js`:
- **What the database said.** Every uncaught error of a method or publication
passes `Meteor._debug`; one whose text looks like a database or process
resource failure (MongoDB, SQLite, PostgreSQL, MySQL, MariaDB, SAP HANA,
`SQLSTATE`, out of memory, `EMFILE`, read-only filesystem, a malformed
database image, an oversized document) is recorded. The startup, process
error and busy-write retry handlers record theirs too.
- **What WeKan measured.** The database health probe
(`server/lib/databaseHealth.js`, at startup and every five minutes on one
server of the installation) records restarts, a data directory on a network
filesystem, storage latency and disk space running out; startup records an
index it had to create (`server/lib/mongoStartup.js`).
Each message is classified by the pure rules in `models/lib/databaseErrors.js`
(for example `connection-lost`, `disk-full`, `auth-failed`, `mysql-syntax`,
`deadlock`, `timeout`, `duplicate-key`, `database-corrupt`,
`memory-exhausted`, and `unclassified` for anything no rule knows). The same
problem on the same database is recorded at most once a minute.
A FerretDB **canary** - an operation WeKan never issues, such as server-side
JavaScript, dropping a database or SQL that looks injected - is not a database
problem: it goes to the [Security Report](Security-Report.md) instead.
## The table
The same read-only event table as the other streams
([Security Report](Security-Report.md)), newest first, 10 rows a page, with a
search box that filters as you type. On this stream:
| Column | Holds |
| --- | --- |
| Category | which database: `mongodb`, `sqlite`, `postgresql`, `mysql`, `mariadb`, `hana` or `unknown` |
| Name | the kind of problem, for example `disk`, `auth`, `syntax`, `timeout` or `health` |
| Severity | the rule's severity |
| Action | the classifier's rule id |
| Source | the operation, or `Meteor._debug`, or `health` |
| Detail | what it means and what to do, then `—` and what the database itself said |
The search also finds the database name, the rule id and words of the
database's own message.
Acknowledge or clear the stream on [Summary](Summary.md). Rows older than
`EVENTLOG_RETENTION_DAYS` (default 90) are deleted daily. The rows are also on
`GET /api/admin/problems/database`
([REST API](../../../API/REST-API.md#admin-panel-problems)).
## Related
- [Supported databases](../../../Databases/Supported.md)
- [Recovery.md](Recovery.md) - SQLite corruption and the recovery history.
- [FerretDB remediation design](../../../Security/Remediation/FerretDB.md) -
the database canaries.
@@ -0,0 +1,56 @@
# Admin Panel / Problems / Filesystem integrity
Whether this server stopped cleanly, what crashed it, and whether the
continuous backup failed - plus the read-only file status checks. Address:
`/admin/problems/integrity`. Site administrators only.
## File status checks
At the top of the pane, the same checks as on the Files Report and Recovery
panes: **Check files and history**, **Check file types and extensions** and
**Check missing and untracked files**, with **Cancel check** while one runs and
**Download status summary** when one has finished. They change no file and no
record. See [File-status.md](File-status.md).
## Where the rows come from
The `integrity` stream of the `eventlog` collection:
| Name | Severity | Recorded when | Written by |
| --- | --- | --- | --- |
| `DowntimeBleed` (category `availability`) | `high` | the previous run left no clean-shutdown mark and the server was down for more than three minutes: a crash | `server/lib/uptimeWatch.js` |
| `DowntimeBleed` (category `availability`) | `low` | no clean-shutdown mark, but back within three minutes: a quick restart | `server/lib/uptimeWatch.js` |
| `CrashBleed` (category `crash`) | `critical` | an uncaught exception or an unhandled promise rejection, with its message | `server/lib/uptimeWatch.js` |
| `ContinuousBackup` (category `backup`) | `high` | the continuous backup stream failed | `server/continuousBackup.js` |
WeKan writes a heartbeat every minute and marks a clean stop on `SIGTERM` or
`SIGINT`; the next start compares the two. A clean stop and a first run are not
recorded. A database that is only momentarily unreachable is not a crash: it is
recorded on [Database problems](Database-problems.md) instead.
The daily scan of stored files (same name, size, modification time, md5,
sha256 and sha512, signed with ed25519) and the hourly change history audit
report what they find to the [Security Report](Security-Report.md), as
**StorageBleed** and **HistoryIntegrity**, not to this stream. They can be
turned off with `WEKAN_INTEGRITY_SCAN=false` and
`WEKAN_HISTORY_INTEGRITY_SCAN=false`; `WEKAN_INTEGRITY_PRIVATE_KEY` supplies the
signing key instead of one generated and kept in the database.
## The table
The same read-only event table as the other streams
([Security Report](Security-Report.md)): Date and time, Category, Name,
Severity, Action, Source, Username, IPv4, Location, IPv6, Location, Attempts
and Detail, newest first, 10 rows a page, with a search box that filters as you
type.
Acknowledge or clear the stream on [Summary](Summary.md). Rows older than
`EVENTLOG_RETENTION_DAYS` (default 90) are deleted daily. The rows are also on
`GET /api/admin/problems/integrity`
([REST API](../../../API/REST-API.md#admin-panel-problems)).
## Related
- [Security remediation design](../../../Security/Remediation/WeKan.md),
section 13.
- [Continuous backup](../../../Backup/Backup.md)
@@ -0,0 +1,41 @@
# Admin Panel / Problems / Impersonation Report
Every time an administrator acted as another user, and why. Address:
`/admin/problems/impersonation`. Site administrators only: the publication
sends nothing, and the count method refuses, for anybody who is not
`isAdmin`.
## Where the rows come from
The `impersonatedUsers` collection. A row is written when:
| Reason | Written when |
| --- | --- |
| `clickedImpersonate` | an administrator impersonates a user from Admin Panel / People (the `impersonate` method) |
| `restCreateToken: <reason>` | an administrator creates a login token for another user through the REST API; the reason is required and kept, up to 500 characters |
| `exportJSON`, `exportJSONattachment`, `exportExcel`, `exportExcelCard`, `exportCardPDF`, or the export type | a board, card or attachment is exported while impersonating, with the board it was exported from |
Nothing in this pane deletes or changes a row.
## The table
The shared [table page](../../General/Table.md), newest first, 10 rows a page,
fetched one page at a time from the server (`impersonationReport` publication,
`getImpersonationReportCount` method):
| Column | Holds |
| --- | --- |
| Date | when it happened |
| Admin | the administrator; click the name for the Edit user popup |
| Impersonated user | the user acted as, when there was one; click for Edit user |
| Board | the board id, for exports |
| Reason | one of the reasons above |
The search box applies when Enter is pressed. It matches, case-insensitively,
the admin, user, board and attachment ids and the reason
(`models/lib/impersonationReportQuery.js`) - ids, not user names.
## Related
- [People](../People/People.md) - where impersonation starts.
- [REST API](../../../API/REST-API.md)
@@ -0,0 +1,36 @@
# Admin Panel / Problems / Performance
How WeKan loads a board's cards. Address: `/admin/problems/performance`. Site
administrators only. The pane is a description, with nothing to click or
save: it sits beside Speed, Tests and CPU usage because it is what decides how
much a big board costs to open.
## What it says
**Card loading** is automatic, per board, by size (`models/lib/cardsLoading.js`):
- a board with more than the threshold of cards (default **500**) loads lazily:
each list loads only the cards that are visible (infinite scroll) and the
counts come from the server;
- a smaller board loads every card, for the simplest and fully featured
behaviour.
## Environment variables
There is no setting in the Admin Panel. Operators can force a mode:
| Variable | Values | Default |
| --- | --- | --- |
| `CARDS_LOADING` | `auto`, `all` or `lazy`; anything else is `auto` | `auto` |
| `CARDS_LOADING_LAZY_THRESHOLD` | a card count; `0` makes every `auto` board lazy; an invalid or negative value is the default | `500` |
`all` sends every non-archived card of a board to each viewer; filtering,
search, counts, sorting and drag and drop then run in the browser. `lazy`
sends only the visible window of each list, through a windowed publication per
list.
## Related
- [Large-Boards.md](Large-Boards.md) - what a large board loads, and the
measurements behind the threshold.
- [Speed](Speed.md) and [CPU usage](CPU-usage.md).
@@ -58,11 +58,17 @@ sample stream into just two events per episode, with **hysteresis** to prevent
flapping:
- enter the high state after `WEKAN_RAM_HIGH_SAMPLES` (3) consecutive samples at/above
`WEKAN_RAM_HIGH_PERCENT` (default 90% RAM used) **OR** at/above
`WEKAN_SWAP_HIGH_PERCENT` (default 25% swap used — any real swapping is already a
performance problem);
`WEKAN_RAM_HIGH_PERCENT` (default 90% RAM used), **or** with swap at/above
`WEKAN_SWAP_HIGH_PERCENT` (default 25% swap used) **while RAM is also** at/above
`WEKAN_RAM_LOW_PERCENT` (default 80%);
- leave it after `WEKAN_RAM_LOW_SAMPLES` (3) consecutive samples with RAM below
`WEKAN_RAM_LOW_PERCENT` (default 80%) and swap below the swap threshold;
`WEKAN_RAM_LOW_PERCENT`.
Swap alone is not memory pressure. A machine running many programs keeps their
idle pages in swap while plenty of RAM is free; a developer laptop at RAM 52% and
swap 60% used to be reported as "high RAM usage started (>= 90%)", high severity.
Swap now counts only when RAM is tight as well, and the start row says which of
the two started it: `(RAM >= 90%)` or `(swap >= 25% with RAM >= 80%)`.
- it tracks the peak RAM% and peak swap% seen during the episode for the end row.
### Report — Admin Panel → Problems → Memory Usage
@@ -71,13 +77,15 @@ Episodes are written to the `eventLog` collection on the **`ram`** stream (a new
`securityCategories`-style stream alongside `cpu`), and shown by the existing
`eventStreamReport` template (paginated, searchable, read-only). Two rows per episode:
- **start** (`detected`): `high RAM usage started (>= 90%): RAM 7.4/8.0 GB (92%),
- **start** (`detected`): `high RAM usage started (RAM >= 90%): RAM 7.4/8.0 GB (92%),
swap 0.6/2.0 GB (30%), load …, WeKan: <activity>`
- **end** (`remediated`): `high RAM usage ended after 42s (peak RAM 96%, peak swap
41%, back under 80%): RAM 5.1/8.0 GB (64%), swap 0.1/2.0 GB (5%)`
Severity: `high` when RAM is at ≥ 95% or swap is at/above its threshold when the
period starts, else `medium`. The end row is `info`, so it does not count as a new
Severity: `high` when RAM is at ≥ 95% when the period starts, else `medium`. The
rows are named `HighRamUsage` (they were `RamBleed`, as if they were a
vulnerability; the old rows are renamed at startup) and carry no CWE: this is how
busy the machine is, not an attack. The end row is `info`, so it does not count as a new
problem.
Above the rows, a live line shows the current RAM use (percentage and used / total
+52 -60
View File
@@ -18,60 +18,53 @@ stream, `GET /api/admin/problems/:stream` one page of a stream, and
## The Status overview (Problems → Summary)
The **Summary** tab shows a **Status** overview at the top:
The **Summary** pane ([Summary.md](Summary.md)) shows a **Status** overview at
the top:
- **In progress** — every migration or repair running right now (database text
migration, board data-repair, recovery/maintenance, cron migration, attachment
migration), gathered from the persisted status collections so it is accurate even
across a restart.
- **Problems** — detected issues: broken cards, and any failing login-page check.
- **Login page checks** — the known causes that make the login page show
**"Must be logged in"** or sit on the logo + **"Loading, please wait."** spinner
(see **[Login-Problems.md](Login-Problems.md)**).
migration, board data-repair, recovery/maintenance, attachment migration),
gathered from the persisted status collections so it is accurate even across
a restart.
- **Problems** — detected issues: broken cards, lists missing their swimlane, a
failed or overdue backup, data health findings, and any failing login-page
check — the known causes that make the login page show **"Must be logged
in"** or sit on the logo + **"Loading, please wait."** spinner (see
**[Login-Problems.md](Login-Problems.md)**).
Below that is the acknowledge list of the Security / Speed / Tests problem streams.
The Security Report also records denied passwordless code requests after five
requests per source address in one minute. Meteor's per-connection Accounts
limit still applies independently.
Attempts that Meteor 3.5.3's security fixes refuse - a crashing DDP message,
a `__proto__` update field, a malformed `import()` request, an OAuth token of
another application - are recorded as **Meteor DDP**, **Meteor allow-deny**,
**Meteor dynamic-import** and **Meteor OAuth**
([details](../../../Security/Meteor-3.5.3-Security-Fixes-2026-10-22.md)).
An import or export refused by the transfer boundary (a cycle, a non-plain
object, a size limit) is **ImportExportValidation**. One that failed for
another reason - a library that threw, as sanitize-html 2.18.0 did on nested
`<iframe>` - is **ImportExportFailure**: detected, never an attempt, and it
never disables the account of the user whose import or export it was.
Below that are the data health scan and the acknowledge / clear list of the
problem streams. What each stream records is on its own page: the Security
Report also records denied passwordless code requests, the Meteor 3.5.3
refusals and import / export validation, see
[Security-Report.md](Security-Report.md).
## The menu, in two named groups
## The menu
**Settings** — the panes that hold server-wide feature switches, which are
settings rather than reports but are what an admin reaches for when something is
unsafe or noisy:
Admin Panel / Problems opens on **Summary**, then **Backup**, then the
**Reports** group.
- **Security** — how rich text is rendered (links as plain text, all code as plain
text) and the import / export privacy switches (disable all import / export,
avatars, anonymize users). All enforced server-side.
- **Delete** — allow Global Admins to permanently purge soft-deleted content.
The switch is off by default and enabling it deletes nothing by itself.
- **Notifications** — disable all activities, all notifications, or watching, for
deployments that must limit activity tracking
([#5820](https://github.com/wekan/wekan/issues/5820)).
**Security**, **Delete** and **Notifications** used to be a "Settings" group
here. They are settings, not problems, and on 2026-11-19 they moved to Admin
Panel / Settings as [Security](../Settings/Security.md),
[Delete](../Settings/Delete.md) and
[Activities and notifications](../Settings/Activities-and-Notifications.md).
Their old `/admin/problems/...` addresses redirect there.
- **Summary** — what is running, what is wrong, and the new-problem count of
each stream, with the repair, acknowledge and clear buttons.
- **Backup** — did the Admin Panel backup work: the last successful backup,
the last failure and its error, the next scheduled run, and the history of
the last runs. Its settings stay in Admin Panel / Attachments / Backup; a
failed or overdue backup is also listed on Summary
([Backup.md](../../../Backup/Backup.md)).
**Reports** — Security Report, Impersonation Report, Password length, Performance, Speed, Tests, CPU
usage, Instrumentation, Broken Cards, Files Report, Rules Report, Boards Report,
Cards Report, Recovery, Offices, API, Database problems, Filesystem integrity and
Email.
Report tables use the shared [table page](../../General/Table.md):
a search box, the total, `page X / N`, prev/next, and one page of rows fetched from
the server at a time. **Performance** sits with the Speed / Tests / CPU usage streams
it configures: card loading is automatic per board size, with
**Reports** — Security Report, Impersonation Report, Password length,
Performance, Speed, Tests, CPU usage, Memory Usage, Disk usage,
Instrumentation, Broken Cards, Files Report, Rules Report, Boards Report, Cards
Report, Recovery, Offices, API, Database problems, Filesystem integrity and
Email. Report tables use the shared [table page](../../General/Table.md): a
search box, the total, `page X / N`, prev/next, and one page of rows fetched
from the server at a time. **Performance** sits with the Speed / Tests / CPU
usage streams: card loading is automatic per board size, with
`CARDS_LOADING=all|lazy|auto` and `CARDS_LOADING_LAZY_THRESHOLD` for operators.
## Detailed pages in this directory
@@ -117,39 +110,38 @@ rather than what it shows.
Every pane of this tab, in the order the menu shows them. The slug is what
the address uses: `/admin/problems/<slug>`.
Security, Delete and Notifications are no longer in this list: they moved to
Admin Panel / Settings (see [The menu](#the-menu) above).
| Menu path | URL slug | Page |
| --- | --- | --- |
| Problems / Summary | `summary` | — |
| Problems / Security | `security` | — |
| Problems / Delete | `delete` | — |
| Problems / Notifications | `notifications` | — |
| Problems / Summary | `summary` | [Summary.md](Summary.md) |
| Problems / Backup | `backup` | [Backup.md](../../../Backup/Backup.md#did-the-backup-work-history-health-and-monitoring) |
| Problems / Security Report | `security-report` | — |
| Problems / Impersonation Report | `impersonation` | — |
| Problems / Security Report | `security-report` | [Security-Report.md](Security-Report.md) |
| Problems / Impersonation Report | `impersonation` | [Impersonation-Report.md](Impersonation-Report.md) |
| Problems / Password length | `password-length` | [Password-length.md](Password-length.md) |
| Problems / Performance | `performance` | — |
| Problems / Speed | `speed` | — |
| Problems / Tests | `tests` | — |
| Problems / Performance | `performance` | [Performance.md](Performance.md) |
| Problems / Speed | `speed` | [Speed.md](Speed.md) |
| Problems / Tests | `tests` | [Tests.md](Tests.md) |
| Problems / CPU usage | `cpu` | [CPU-usage.md](CPU-usage.md) |
| Problems / Memory Usage | `ram` | [RAM-usage.md](RAM-usage.md) |
| Problems / Disk usage | `disk` | [Disk-usage.md](Disk-usage.md) |
| Problems / Instrumentation | `instrumentation` | [Instrumentation.md](Instrumentation.md) |
| Problems / Broken Cards | `broken-cards` | — |
| Problems / Broken Cards | `broken-cards` | [Broken-Cards.md](Broken-Cards.md) |
| Problems / Files Report | `files` | [File-status.md](File-status.md) |
| Problems / Rules Report | `rules` | — |
| Problems / Boards Report | `boards` | — |
| Problems / Cards Report | `cards` | — |
| Problems / Rules Report | `rules` | [Rules-Report.md](Rules-Report.md) |
| Problems / Boards Report | `boards` | [Boards-Report.md](Boards-Report.md) |
| Problems / Cards Report | `cards` | [Cards-Report.md](Cards-Report.md) |
| Problems / Recovery | `recovery` | [Recovery.md](Recovery.md) |
| Problems / Offices | `office` | [Offices.md](Offices.md) |
| Problems / API | `api` | [API.md](API.md) |
| Problems / Database problems | `database` | — |
| Problems / Filesystem integrity | `integrity` | — |
| Problems / Database problems | `database` | [Database-problems.md](Database-problems.md) |
| Problems / Filesystem integrity | `integrity` | [Filesystem-integrity.md](Filesystem-integrity.md) |
| Problems / Email | `mail` | [Bounces.md](../../General/Email/Bounces.md#when-something-goes-wrong) |
15 of these 26 panes has no page of its own yet. A dash is a
gap to fill, not a pane that does nothing - what the pane shows is described in
this README until somebody writes it up.
0 of these 23 panes has no page of its own: every pane above links one. A pane
added to the menu without a page gets a dash here and is counted in this
sentence.
[File status checks](File-status.md): inspect missing files, incomplete upload
metadata, detected types, storage references and available recovery evidence.
@@ -0,0 +1,25 @@
# Admin Panel / Problems / Rules Report
Every automation rule on the instance, with its board, trigger and action.
Address: `/admin/problems/rules`. Site administrators only.
## The table
The shared [table page](../../General/Table.md), 10 rows a page, sorted by
board, fetched one page at a time from the server (`rulesReport` publication,
`getRulesReportCount` method, `server/publications/rules.js`):
| Column | Holds |
| --- | --- |
| Rule Title | the rule's title |
| Board Title | the board the rule belongs to |
| actionType | the type of the rule's action |
| activityType | the activity type of the rule's trigger |
The search box applies when Enter is pressed and matches the rule title,
case-insensitively. The pane is read-only: rules are edited on their board.
## Related
- [Rules](../../Automation/Rules/Rules.md)
- [Rules REST API](../../../API/Rules.md)
@@ -0,0 +1,76 @@
# Admin Panel / Problems / Security Report
Every attempt a security guard refused or noticed: what it was, how severe,
who tried it, from where and how many times. Address:
`/admin/problems/security-report`. Site administrators only. It is called
Security Report, not Security, because Admin Panel / Settings /
[Security](../Settings/Security.md) is the pane of security switches.
## Where the rows come from
The `security` stream of the `eventlog` collection (`models/eventLog.js`).
Every runtime guard reports through `server/lib/securityLog.js` when it blocks,
sanitizes, rate-limits or detects something, using a key from the catalog in
`models/lib/securityCategories.js` (category, Hall of Fame name, severity,
CWE). Besides the guards, this stream also receives:
- the canaries - operations WeKan never issues, such as a database canary
marked by FerretDB (`server/lib/databaseProblems.js`);
- the daily filesystem integrity scan's findings (`integrity.file`,
**StorageBleed**, `server/lib/fileIntegrityScan.js`) and the hourly change
history audit (`integrity.history`, **HistoryIntegrity**,
`server/lib/historyIntegrityScan.js`);
- denied passwordless code requests after five requests per source address in
one minute;
- the Meteor 3.5.3 refusals, recorded as **Meteor DDP**, **Meteor allow-deny**,
**Meteor dynamic-import** and **Meteor OAuth**
([details](../../../Security/Meteor-3.5.3-Security-Fixes-2026-10-22.md));
- **ImportExportValidation** (an import or export refused by the transfer
boundary) and **ImportExportFailure** (one that failed for another reason,
recorded as detected, never as an attempt).
Each problem is one row that accumulates (`server/lib/eventLogFold.js`): the
kind of thing that happened is the row, and the user name and address describe
its most recent occurrence ([Design.md](Design.md)).
## Consequence for the account
When a row is `blocked`, of severity `high` or `critical`, names a logged-in
user and its catalog key does not say otherwise, that account is disabled
(`loginDisabled`) with the reason "Attempted <name> at <source> while logged
in" (`server/lib/blockOnSecurityEvent.js`). The address is recorded, never
blocked. An administrator re-enables the account in Admin Panel /
[People](../People/People.md).
## The table
The shared [table page](../../General/Table.md), newest row first, 10 rows a
page, read-only:
| Column | Holds |
| --- | --- |
| Date and time | when it last happened |
| Category | the guard's class, for example `ssrf` or `integrity` |
| Name | the Hall of Fame name (`...Bleed`) or another fixed name |
| Severity | `info`, `low`, `medium`, `high` or `critical` |
| Action | `blocked`, `sanitized`, `rate-limited`, `remediated`, `detected` or `failed` |
| Source | the guard or module that recorded it |
| Username | the account, as it was called at the time; click it for the Edit user popup |
| IPv4, Location, IPv6, Location | the address, resolved with `HTTP_FORWARDED_COUNT`, and a location only when a trusted proxy supplies one |
| Attempts | how many times this row happened; empty when once |
| Detail | what the guard said |
The search box filters as you type, case-insensitively, over category, name,
source, detail, username and address. The rows come from the admin-only
`eventLogCount` and `eventLogPage` methods.
Nothing is acknowledged here: the new-problem count is acknowledged or the
stream cleared on [Summary](Summary.md). Rows older than
`EVENTLOG_RETENTION_DAYS` (default 90) are deleted daily. The same rows are on
`GET /api/admin/problems/security`
([REST API](../../../API/REST-API.md#admin-panel-problems)).
## Related
- [Security remediation design](../../../Security/Remediation/WeKan.md)
- [Hall of Fame](https://wekan.fi/hall-of-fame/) - the names in the Name column.
@@ -0,0 +1,41 @@
# Admin Panel / Problems / Speed
HTTP requests that took too long. Address: `/admin/problems/speed`. Site
administrators only.
## Where the rows come from
The `speed` stream of the `eventlog` collection. Today one detector writes it:
`server/lib/speedMiddleware.js` times every HTTP request that is not a static
asset (`.js`, `.css`, images, fonts, source maps) or under `/cdn/`, and when one
takes at least `WEKAN_SLOW_REQUEST_MS` milliseconds (default `2000`; `0` turns
the detector off) it records, through `server/lib/speedLog.js`:
- category `slow-request`, name `SlowRequest`, action `detected`, source `http`;
- severity `low`, or `medium` when it took three times the threshold or more;
- detail `<METHOD> <path> — <ms>ms >= <threshold>ms`, without the query string.
DDP methods and publications are not timed here; their live call counts and
durations are on [Instrumentation](Instrumentation.md). The CPU monitor writes
its own stream, shown on [CPU usage](CPU-usage.md).
The same request path that is slow again is folded into the same row, whose
count and date go up ([Design.md](Design.md)).
## The table
The same read-only event table as the [Security Report](Security-Report.md):
Date and time, Category, Name, Severity, Action, Source, Username, IPv4,
Location, IPv6, Location, Attempts and Detail, newest first, 10 rows a page,
with a search box that filters as you type. It shows "No new problems." when the
stream is empty.
Acknowledge or clear the stream on [Summary](Summary.md). Rows older than
`EVENTLOG_RETENTION_DAYS` (default 90) are deleted daily. The rows are also on
`GET /api/admin/problems/speed`
([REST API](../../../API/REST-API.md#admin-panel-problems)).
## Related
- [Performance](Performance.md) - how boards load their cards.
- [Large-Boards.md](Large-Boards.md)
@@ -0,0 +1,83 @@
# Admin Panel / Problems / Summary
The first pane of Admin Panel / Problems, and the one it opens on: what is
running now, what is wrong now, and how many new problems each problem stream
has. Address: `/admin/problems/summary` (the bare `/admin/problems` and the old
`/admin-reports` open it too). Site administrators only: the page shows "not
authorized" to anybody else, and every method behind it refuses a caller who is
not `isAdmin`. Organization administrators do not see it.
The pane reloads itself every 30 seconds. The same overview is printed by
`snap run wekan.problems` ([Snap.md](Snap.md)) and returned by
`GET /api/admin/problems` ([REST API](../../../API/REST-API.md#admin-panel-problems)).
## Status
From the `systemStatusReport` method (`server/methods/systemStatus.js`,
`server/lib/systemStatus.js`, `models/lib/problemsOverview.js`).
**In progress** - every migration or repair that is running now, read from the
persisted status collections so it is right after a restart too:
- the database text migration (MongoDB to and from FerretDB v1), with its
direction and phase ([Migrations.md](Migrations.md));
- the board data-repair, as `done/total` boards ([Repairs.md](Repairs.md));
- data recovery / maintenance;
- an attachment migration or repair.
When nothing runs, the pane says "No migrations or repairs are in progress."
While something does, it says logins can be slow until it finishes.
**Problems** - each detected problem as a line with its count and detail:
| Problem | Button | What the button does |
| --- | --- | --- |
| Broken cards - cards with no board, swimlane or list, or an invalid type | **Repair broken cards** | Runs the `repairBrokenCards` method over every board, then says how many were fixed and how many cannot be placed on any board (no board id at all). |
| Lists missing their swimlane ([#6670](https://github.com/wekan/wekan/issues/6670)) | **Restore** | Runs `restoreListSwimlanes`: puts each list back in the swimlane it was created in, where that is still recorded and still exists, and says how many were restored and how many remain board-wide. |
| A failing login-page check | - | Configuration, not data; the detail says what to change ([Login-Problems.md](Login-Problems.md)). |
| A failed or overdue Admin Panel backup | - | See [Backup](../../../Backup/Backup.md#did-the-backup-work-history-health-and-monitoring). |
| A data health finding | **Repair** | Runs `repairDataHealth` for that check. A repair that only moves data runs on one click; one that deletes data first turns into **Confirm** and runs on the second click ([Data-Health.md](Data-Health.md)). |
Every button is disabled while its repair runs, and the overview reloads when
it is done so the count changes straight away.
## Data health
The last run of the nightly read-only data health scan, as
`<date> UTC - <checks that found something>/<checks>`, or that it has never
run. **Start** runs the scan now (`dataHealthScanNow`); it runs in the
background and its findings appear under Problems above
([Data-Health.md](Data-Health.md)).
## Problems (the event streams)
One checkbox line per event stream with problems newer than its last
acknowledgement, written as the menu path
(`Admin Panel → Problems → Security Report`) with its count of new problems.
The streams are `security`, `speed`, `tests`, `cpu`, `ram`, `disk`, `database`,
`integrity` and `mail` (`EVENT_STREAMS` in `models/eventLog.js`); the API usage
report is not one of them. A row with severity `info` is never counted as a new
problem (`models/lib/eventLogProblems.js`), so a CPU spike that only records
its own mitigation does not raise the count.
Tick the streams you have reviewed, then:
- **Acknowledge** (`acknowledgeEventLog`) - resets the new-problem count of each
ticked stream. The rows stay in its pane.
- **Clear** (`clearEventLog`,
[#6893](https://github.com/wekan/wekan/issues/6893)) - deletes every row of
each ticked stream up to now and acknowledges it. A problem that happens
again after the click shows as new again.
This is the only place problems are acknowledged or cleared; the stream panes
themselves are read-only. With nothing new, the section says "No new problems."
Rows also age out by themselves after `EVENTLOG_RETENTION_DAYS` days (default
`90`, `0` keeps them for ever), checked once a day for the whole installation.
## Related
- [README.md](README.md) - every Problems pane.
- [Design.md](Design.md) - why each problem is one summary row.
- [Security remediation design](../../../Security/Remediation/WeKan.md) - the
event log behind the streams.
@@ -0,0 +1,43 @@
# Admin Panel / Problems / Tests
Runtime self-checks that failed: the kind of invariant a WeKan unit test
asserts, checked on the running server without a browser and without
Playwright. Address: `/admin/problems/tests`. Site administrators only.
## Where the rows come from
The `tests` stream of the `eventlog` collection, written by
`server/lib/selfChecks.js` through `server/lib/testLog.js`. The checks run once,
15 seconds after the server starts. Only a failure is recorded; a passing check
writes nothing.
| Check (Source column) | Fails when |
| --- | --- |
| `self-check:database-roundtrip` | a one-document query to the database fails |
| `self-check:writable-path` | a probe file cannot be written and removed in `WRITABLE_PATH/files` |
| `self-check:heap-headroom` | the V8 heap uses 90 % or more of its limit |
| `self-check:free-disk-space` | the files filesystem has less free space than `WEKAN_MIN_FREE_DISK_MB` (default 256 MiB) |
A failure is recorded with category `test-failure`, name `TestBleed`, action
`failed` and severity `medium`; the Detail column is the check's error message.
The admin-only method `runSelfChecks` runs the checks again on demand. The pane
itself has no button for it.
## The table
The same read-only event table as the [Security Report](Security-Report.md):
Date and time, Category, Name, Severity, Action, Source, Username, IPv4,
Location, IPv6, Location, Attempts and Detail, newest first, 10 rows a page,
with a search box that filters as you type. "No new problems." means no check
has failed since the stream was last cleared.
Acknowledge or clear the stream on [Summary](Summary.md). Rows older than
`EVENTLOG_RETENTION_DAYS` (default 90) are deleted daily. The rows are also on
`GET /api/admin/problems/tests`
([REST API](../../../API/REST-API.md#admin-panel-problems)).
## Related
- [RAM-usage.md](RAM-usage.md) and [Disk-usage.md](Disk-usage.md) - the
continuous memory and disk monitors.
@@ -0,0 +1,25 @@
# Admin Panel / Settings / Activities and notifications
For deployments that must limit activity tracking
([#5820](https://github.com/wekan/wekan/issues/5820)). Address:
`/admin/settings/activities`. Site administrators only. Each switch is saved as
soon as it is ticked and is off by default.
Until 2026-11-19 this pane was Admin Panel / Problems / Notifications;
`/admin/problems/notifications` redirects here. It is not Admin Panel / People /
Notifications, which is about email notifications.
- **Disable all activities** - activity-feed entries are never recorded and
never shown anywhere (the board sidebar and a card's activity tab). No history
of who did what is kept.
- **Disable all notifications** - WeKan never sends watch notifications (in-app,
email or other services) for any activity. Activities can still be recorded,
unless also disabled above; only the notifications are suppressed.
- **Disable watch** - nobody can watch boards, lists or cards to receive
notifications, and any attempt to change a watch level is refused.
## Related
- [Admin Panel / People / Notifications](../People/Notifications.md) - email
notifications.
- [Security](Security.md)
@@ -1,7 +1,15 @@
# Admin Panel / Settings / Visibility
# Admin Panel / Settings / Appearance
Four groups, each with its own **Save** directly above the rule that closes it. A
Save writes only its own group's fields, so saving one cannot carry half-typed edits
How this WeKan looks: what All Boards shows, dates, the URLs it links to, its
product name, colours and logos. Address: `/admin/settings/appearance`.
Until 2026-11-19 this pane was **Visibility**, and it also held which features
the instance offers. Those are [Features](Features.md) and
[Feature profiles](Feature-Profiles.md) now, and `/admin/settings/visibility`
redirects here.
Each group has its own **Save** directly above the rule that closes it. A Save
writes only its own group's fields, so saving one cannot carry half-typed edits
from another.
## All Boards: Hide
@@ -45,51 +53,6 @@ Each row is ticked when the thing is **hidden**.
- **Wait Spinner** — which spinner is shown while something loads. See
[Wait Spinners](../../General/Troubleshooting/Wait-Spinners.md).
## Features
Which optional features this WeKan offers. An unticked feature is hidden from
everyone's interface; its data is kept and no permission changes.
Besides the board view groups, four
[helpers that need no AI](../../General/Assistants/Assistants.md) are features
here: **Rule suggestions**, **Summary**, **Since your last visit** and
**Search phrases**. The card helpers - Due date from title, Similar cards, At
risk, Suggested members, Forecast, Checklist from description and Action
items - are card fields, below.
### Card fields
Above the Features **Save** there is one tick per field type of the board right
sidebar's **Board Settings / Card** (Received, Start, Due, End, Members, Assignee,
Labels, Description, Checklists, Pomodoro, each Scrum field, and the rest), with the
same icons and names. All are ticked by default.
Unticking a field, for example **Pomodoro**, and saving hides it on every board of
this WeKan:
- its row is not offered in any board's Board Settings / Card;
- it is not shown on any opened card or minicard, whatever the board itself chose.
It is **visibility only**. No card data is deleted or changed, and no board setting
is written: each board keeps its own choice, and ticking the field again shows every
board exactly as it was set. A board admin's whole-column tick in Board Settings /
Card leaves the hidden fields' values alone for the same reason.
There is **no ordering** here: the order of the fields on a card and a minicard is
each board's own, set by drag and drop in Board Settings / Card.
Stored on the settings document as `cardFieldStates` (`{ field: true|false }`;
a missing field is shown), saved by the site-admin-only Features save. The catalog
and the decisions are `models/lib/cardFieldVisibility.js`.
## Optional APIs
Below Features: one tick each for the **Trello**, **Jira**, **GitHub** and
**Gitea** compatible APIs, all off by default, each with what it does and the
address a client uses. They let apps written for those trackers use WeKan as
their backend, with no rights of their own: every call is WeKan's REST API as
the person signed in. See [Optional APIs](../../../API/Optional-APIs.md).
## URL
- **Support** — the link to `/support`, whether the page is enabled, whether it is
@@ -0,0 +1,27 @@
# Admin Panel / Settings / Delete
Whether deleted content can be destroyed for good. Address:
`/admin/settings/delete`. Site administrators only.
Until 2026-11-19 this pane was Admin Panel / Problems / Delete;
`/admin/problems/delete` redirects here.
Deleting in WeKan is a **soft delete**: a deleted list, card or attachment is
marked deleted and can be restored (undo, the card or list History, Admin Panel /
Problems / Recovery). Nothing is destroyed in ordinary use.
**Enable permanent delete for Global Admin** lets Global Admins permanently delete
soft-deleted content - for example a list in the recycle bin, or an archived
board together with its attachments. It is off by default, and turning it on
deletes nothing by itself. GDPR account erasure is a separate path and does not
depend on it.
The permanent-delete setting must be on before a delete icon is shown. Recovery
records setting changes and every successful, failed or unauthorized
permanent-delete attempt, with its Done status, user id, username, trusted IPv4
or IPv6 address and available location; a board deletion records ids and titles.
## Related
- [Admin Panel / Problems / Recovery](../Problems/Recovery.md)
- [Undo](../../General/Undo/Undo.md)
@@ -0,0 +1,151 @@
# Admin Panel / Settings / Feature profiles
A **feature profile** gives chosen users a smaller WeKan: it hides some of the
optional features from the users, teams and organizations it is assigned to.
Everybody else keeps seeing everything.
[#6837](https://github.com/wekan/wekan/issues/6837).
Only a **site administrator** sees and edits feature profiles.
## Where
Admin Panel / Settings / **Feature profiles**, right below
[Features](Features.md) in the Settings menu. Address:
`/admin/settings/feature-profiles`. The pane has its own **Save**; it does not
save the Features ticks, and their Save does not save the profiles. The People,
Teams and Organizations tables of Admin Panel / People show which profile
applies to each person and which profiles a team or organization is named in,
so a profile can be found from either side.
## What a profile can hide
Exactly the features the [Features](Features.md) pane can switch off for the whole
instance - the same list, in the same order:
- the board view groups: Table, Calendar, Time, Overview, Gantt, Scrum, Flow charts,
Map, Email, Chat, Version control, Column sets;
- the helpers that need no AI: Rule suggestions, Summary, Since your last visit and
Search phrases.
Swimlanes and lists are the core of a board and can never be hidden, by a profile or
by the instance.
## Create a profile
1. Open Admin Panel / Settings / Feature profiles.
2. Press **Add profile**. An empty profile appears.
3. **Profile name** - what the profile is called, for example `Newcomers`. Names are
unique (case does not matter) and at most 100 characters. The user sees this name
(see [What the user sees](#what-the-user-sees)), so choose one that means
something to them.
4. **Hide these features** - tick every feature this profile hides. An unticked
feature stays visible.
5. Say who has it - any of the three, or several:
- **Users**: usernames, separated by commas;
- **Teams, one per line**: team names, as in Admin Panel / People / Teams;
- **Organizations, one per line**: organization names, as in Admin Panel /
People / Organizations.
6. Press the section's **Save**.
After saving, the status next to Save says **Saved**, or **Saved. Not found:**
followed by every username, team name or organization name that matched nothing.
Those are not stored, so check their spelling and save again. Everything that did
match is saved.
Up to 50 profiles can exist. Their order on the page is the order they are tried in
(below).
## Change or remove a profile
Edit any field and press **Save**. **Remove profile** takes a profile off the page;
it is gone when you press Save, and its users, teams and organizations then fall
back to whatever else applies to them - usually no profile, so they see everything
again.
Removing a user from the **Users** box of every profile, and saving, takes their
direct profile away.
## Which profile a user has
One profile at most applies to a user, decided in this order:
1. the profile assigned to the user **directly** (their username in **Users**);
2. else the **first** profile in the page's order that names one of the user's
**teams**;
3. else the first profile that names one of the user's **organizations**;
4. else **none** - the user sees everything this WeKan offers.
A username listed in two profiles belongs to the later one: a user has one direct
profile.
## What the user sees
- The hidden features are gone from the interface - for example a hidden board view
is not in the Board View menu - exactly as if the instance had switched them off.
- The **member menu** (top right, the user's avatar) opens with a note: *Your
feature profile Newcomers hides 3 features. Ask an administrator if you need one
of them.* So a user always knows a feature is hidden on purpose, and who to ask.
- A profile that hides nothing shows no note.
The user cannot change or remove their own profile: only a site administrator saves
profiles.
## What a profile does not do
Profiles are **opt-in**. A Simple/Advanced mode that hid features by default was
tried and removed, because a feature missing by default is a support nightmare.
So:
- **Nobody without a profile is affected.** Adding the first profile changes
nothing for anyone until it is assigned to somebody.
- **It only hides.** No card, board or setting is deleted or changed. Removing the
profile shows everything exactly as it was.
- **It is not access control.** A profile never grants or takes away a permission:
a hidden feature's data is still the user's, and other rights - board roles, list
role exceptions, Admin Panel access - are unchanged. Use board roles for who may
do what.
- **It does not override the instance.** A feature the instance switched off stays
off for everyone; a profile can only hide more.
## Pilot users and site administrators
Pilot users (the **Pilot users who also see disabled features** box in
[Features](Features.md), and site administrators when **Administrators see
disabled features, to try them first** is ticked) see the features the instance
switched off. A feature profile still applies to them, because it was assigned to
them on purpose. To test a profile, assign it to yourself and open your member menu.
## When somebody says a feature is missing
1. Ask them to open their member menu. If it says *Your feature profile ... hides*,
the profile is the reason.
2. In Admin Panel / Settings / Feature profiles, find that profile, untick the feature
(or move the user to another profile, or out of it) and **Save**.
3. If the member menu shows no note, the feature is switched off for the whole
instance ([Features](Features.md)), or the board itself does not show it
(Board Settings).
## Technical details
- Stored on the settings document as `featureProfiles`:
`[{ _id, name, hidden: [featureKey], teamIds, orgIds }]`, published to every
client (it holds no secret: names, feature keys and team/organization ids).
- A direct assignment is `featureProfileId` on the user, published only to that
user. Clients may write only `username` and `profile.*` of their own user
document, so a user cannot set or clear it.
- Saved by the site-admin-only methods `getFeatureProfiles` and
`saveFeatureProfiles` (`server/methods/instanceFeatures.js`), which resolve the
names to ids and report the ones that match nothing.
- The decision is `models/lib/featureProfiles.js`, used by `isFeatureAvailable` in
`models/lib/instanceFeatures.js` - the same function every place that hides a
disabled feature already asks, on the client and on the server.
- Tests: `tests/featureProfiles.test.cjs`,
`tests/playwright/specs/feature-profiles.e2e.js`.
## Related
- [Admin Panel / Settings / Features](Features.md) - the features a profile
chooses from.
- [Admin Panel / People / Teams](../People/Teams.md) and
[Organizations](../People/Organizations.md) - the groups a profile can be assigned
to.
@@ -0,0 +1,96 @@
# Admin Panel / Settings / Features
What this WeKan offers. Address: `/admin/settings/features`. Site administrators
only. Until 2026-11-19 these groups were part of Settings / Visibility (now
[Appearance](Appearance.md)).
The pane has four groups, top to bottom: **Features**, **Rules** and **Optional
APIs**, plus the two optional sign-in and publishing features below the Features
Save. Who among your users sees a feature is decided one level down, by
[Feature profiles](Feature-Profiles.md).
## Features
Which optional features this WeKan offers. An unticked feature is hidden from
everyone's interface; its data is kept and no permission changes.
Besides the board view groups, four
[helpers that need no AI](../../General/Assistants/Assistants.md) are features
here: **Rule suggestions**, **Summary**, **Since your last visit** and
**Search phrases**. The card helpers - Due date from title, Similar cards, At
risk, Suggested members, Forecast, Checklist from description and Action
items - are card fields, below.
### Card fields
Above the Features **Save** there is one tick per field type of the board right
sidebar's **Board Settings / Card** (Received, Start, Due, End, Members, Assignee,
Labels, Description, Checklists, Pomodoro, each Scrum field, and the rest), with the
same icons and names. All are ticked by default.
Unticking a field, for example **Pomodoro**, and saving hides it on every board of
this WeKan:
- its row is not offered in any board's Board Settings / Card;
- it is not shown on any opened card or minicard, whatever the board itself chose.
It is **visibility only**. No card data is deleted or changed, and no board setting
is written: each board keeps its own choice, and ticking the field again shows every
board exactly as it was set. A board admin's whole-column tick in Board Settings /
Card leaves the hidden fields' values alone for the same reason.
There is **no ordering** here: the order of the fields on a card and a minicard is
each board's own, set by drag and drop in Board Settings / Card.
Stored on the settings document as `cardFieldStates` (`{ field: true|false }`;
a missing field is shown), saved by the site-admin-only Features save. The catalog
and the decisions are `models/lib/cardFieldVisibility.js`.
### Approval and pilot users
- **Keep features added by WeKan updates disabled until an administrator enables
them** - when on, a feature that a later WeKan update adds stays off until you
tick it here; the features on the page when you turned it on are not affected.
- **Administrators see disabled features, to try them first** - site
administrators keep seeing the features unticked here.
- **Pilot users who also see disabled features** - usernames, separated by
commas, of people who also keep seeing them. A name that matches nobody is
reported after saving.
The Features ticks, the approval policy, the pilot users and the card fields are
saved together by the group's **Save**.
### SQRL and ActivityPub
Below that Save, two optional features that are saved as soon as they are
switched, both off by default:
- **Sign in with SQRL** - the sign-in page offers SQRL, and members add their
SQRL identity in Member Settings first. SQRL needs WeKan at an `https://`
address.
- **Public boards publish their card activity on the fediverse (ActivityPub)** -
each public board can be followed from Mastodon and other fediverse servers as
`@board-<id>` at this WeKan's address, and new card activity reaches its
followers. Read-only: nothing a fediverse server sends changes a board, and
private boards are never published.
## Rules
**Boards may show their Rules to members, read-only.** Off: only board admins see
a board's Rules. On: a board admin can tick *Show these Rules to board members* on
the board's Rules page, and members then read the rules and their details without
being able to change them.
## Optional APIs
Below Rules: one tick each for the **Trello**, **Jira**, **GitHub** and
**Gitea** compatible APIs, all off by default, each with what it does and the
address a client uses. They let apps written for those trackers use WeKan as
their backend, with no rights of their own: every call is WeKan's REST API as
the person signed in. See [Optional APIs](../../../API/Optional-APIs.md).
## Related
- [Feature profiles](Feature-Profiles.md) - hide some of these features from
chosen users, teams and organizations.
- [Appearance](Appearance.md) - how this WeKan looks.
+1 -1
View File
@@ -1,7 +1,7 @@
# Admin Panel / Settings / PWA
Was called **Layout**. Everything that was in it about branding and All Boards moved
to [Visibility](Visibility.md); what is left is what a browser reads about the app
to [Appearance](Appearance.md); what is left is what a browser reads about the app
itself:
- **Custom head tags** — whether they are enabled, plus custom `<meta>` and `<link>`
+13 -1
View File
@@ -3,10 +3,22 @@
The panes of the Settings tab, in menu order. **Version** is first and is the pane
that opens with the Admin Panel.
Settings is **what this WeKan offers and how it looks**: Appearance, then what it
offers (Features) and who sees it (Feature profiles), then the server-wide
switches for security, activity tracking and deletion. Who may sign in and what
they may do is [People](../People/README.md); what is going wrong is
[Problems](../Problems/README.md). How the layers fit together is
[Who sees and can do what](../Who-Sees-What.md).
| Menu path | URL slug | Page | What it is |
| --- | --- | --- | --- |
| Settings / Version | `version` | [Version.md](Version.md) | What this instance is running: WeKan, Meteor, Node, the database and how it is reached. |
| Settings / Visibility | `visibility` | [Visibility.md](Visibility.md) | What All Boards shows, the URLs, the product name and the logos. |
| Settings / Appearance | `appearance` | [Appearance.md](Appearance.md) | How this WeKan looks: what All Boards shows, dates, the URLs, the product name, colours and logos. Was Visibility; `visibility` redirects here. |
| Settings / Features | `features` | [Features.md](Features.md) | Which optional features this WeKan offers, the card fields every board shows, SQRL, ActivityPub, Rules and the Optional APIs. |
| Settings / Feature profiles | `feature-profiles` | [Feature-Profiles.md](Feature-Profiles.md) | Hide some of those features from chosen users, teams and organizations. |
| Settings / Security | `security` | [Security.md](Security.md) | What rich text may do, and what may be imported or exported. Was Problems / Security. |
| Settings / Activities and notifications | `activities` | [Activities-and-Notifications.md](Activities-and-Notifications.md) | Turn off activities, notifications or watching. Was Problems / Notifications. |
| Settings / Delete | `delete` | [Delete.md](Delete.md) | Whether Global Admins may permanently delete soft-deleted content. Was Problems / Delete. |
| Settings / Announcement | `announcement` | [Announcement.md](Announcement.md) | The instance-wide banner. |
| Settings / Accessibility | `accessibility` | [Accessibility.md](Accessibility.md) | The accessibility page and its content. |
| Settings / Translation | `translation` | [Translation.md](Translation.md) | Custom translation strings. |
@@ -0,0 +1,52 @@
# Admin Panel / Settings / Security
Server-wide switches for what rich text may do and what may be imported or
exported. Address: `/admin/settings/security`. Site administrators only. Each
switch is saved as soon as it is ticked, is off by default, and is enforced on
the server - hiding a menu item is never the only thing it does.
Until 2026-11-19 this pane was Admin Panel / Problems / Security;
`/admin/problems/security` redirects here. It is a setting, not a report.
## Rich text
- **Render links as plain text** - every link, both markdown links and raw HTML
`<a href>` tags, is shown as plain, non-clickable text in every rich text
field (board and card titles, descriptions, comments, checklists, ...). This
prevents misleading clickable links.
- **Always show all code as plain text** - rich text is never rendered as
markdown or HTML: the whole source is shown as plain text, which reveals hidden
content - HTML comments, the target of markdown links, JavaScript and any other
code - so nothing is clickable or running.
## Import and export
- **Disable all import** - every import is off: WeKan JSON, Trello, CSV/Excel,
Jira, Kanboard, NextCloud Deck, OpenProject, GitHub, GitLab, Gitea and Forgejo,
and cloning a board. The menu options are hidden and the server refuses any
import request.
- **Disable all export** - every export is off: WeKan JSON, CSV, Excel, Kanboard,
and to NextCloud Deck / OpenProject / GitHub / GitLab / Gitea / Forgejo, and
single-attachment export.
- **Disable import avatars** - profile pictures are never imported: WeKan JSON
and Trello import, and avatar sync from LDAP or OIDC/OAuth2 on login. Names and
other data are still imported.
- **Disable export avatars** - profile pictures are never included in a board
export (WeKan JSON and CSV).
- **Anonymize import users** - importing a WeKan JSON board replaces every
imported user's username, full name and initials with `user1`, `user2`, ...,
drops their avatar, and rewrites `@username` mentions and the requested-by /
assigned-by fields in card and comment content. No real identity from the
source board is stored.
- **Anonymize export users** - the same for exporting: the exported file carries
no real user identity.
The word "user" in the placeholders follows the language of the person importing
or exporting.
## Related
- [Activities and notifications](Activities-and-Notifications.md)
- [Delete](Delete.md)
- [Admin Panel / Problems / Security Report](../Problems/README.md) - what the
security log has recorded.
+6 -4
View File
@@ -52,7 +52,12 @@ are not reachable from the current Admin Panel menu. Current storage panes use
| Pane / URL slug | Implementation | Behavior and limits |
| --- | --- | --- |
| Version (`version`) | [informationBody.js](../../../client/components/settings/informationBody.js) | Live version/runtime information; read-only. |
| Visibility (`visibility`) | [tableVisibilityModeSettings.js](../../../models/tableVisibilityModeSettings.js) | Saved visibility, branding and date defaults; server permissions apply. |
| Appearance (`appearance`) | [tableVisibilityModeSettings.js](../../../models/tableVisibilityModeSettings.js) | Saved All Boards visibility, branding and date defaults; server permissions apply. Was Visibility (2026-11-19). |
| Features (`features`) | [instanceFeatures.js](../../../server/methods/instanceFeatures.js) | Instance features, card fields, pilot users, SQRL, ActivityPub, Rules and Optional APIs; site-admin-only methods. |
| Feature profiles (`feature-profiles`) | [featureProfiles.js](../../../models/lib/featureProfiles.js) | Opt-in profiles hiding features from users, teams and organizations; saved by the site-admin-only saveFeatureProfiles. |
| Security (`security`) | [settings.js](../../../models/settings.js) | Rich-text and import/export policies, enforced by renderers and server guards. Was Problems / Security. |
| Activities and notifications (`activities`) | [settings.js](../../../models/settings.js) | Activity, notification and watching switches; separate from delivery preferences. Was Problems / Notifications. |
| Delete (`delete`) | [settings.js](../../../server/models/settings.js) | Explicit administrator permanent-delete setting; purge remains a separate action. Was Problems / Delete. |
| Announcement (`announcement`) | [announcements.js](../../../models/announcements.js) | Saved banner content and visibility; rendered through announcement controls. |
| Accessibility (`accessibility`) | [accessibilitySettings.js](../../../models/accessibilitySettings.js) | Saved accessibility content and configuration. |
| Translation (`translation`) | [translation.js](../../../server/models/translation.js) | Add/edit/delete custom translation records with administrator checks. |
@@ -106,9 +111,6 @@ are not reachable from the current Admin Panel menu. Current storage panes use
| Pane / URL slug | Implementation | Behavior and limits |
| --- | --- | --- |
| Summary (`summary`) | [systemStatus.js](../../../server/methods/systemStatus.js) | Actual startup/login checks, active migrations and problem streams. |
| Security (`security`) | [settings.js](../../../models/settings.js) | Rich-text and import/export policies, enforced by renderers and server guards. |
| Delete (`delete`) | [settings.js](../../../server/models/settings.js) | Explicit administrator permanent-delete setting; purge remains a separate action. |
| Notifications (`notifications`) | [settings.js](../../../models/settings.js) | Activity, notification and watching switches; separate from delivery preferences. |
| Backup (`backup`) | [backup.js](../../../server/methods/backup.js) | Recorded backup runs, health of the instance backup and its history (backupHistory method); settings stay in Attachments / Backup. |
| Security Report (`security-report`) | [eventLog.js](../../../models/eventLog.js) | Recorded security events, search, detail and acknowledgement. |
| Impersonation Report (`impersonation`) | [impersonationReport.js](../../../server/publications/impersonationReport.js) | Scoped event publication and counts. |
@@ -0,0 +1,54 @@
# Who sees and can do what
WeKan decides "is this here for me?" and "may I do this?" in several places, set by
different people. This page is the map: each layer, who sets it, and how the layers
combine. Every layer links to its own page.
## Two different questions
- **Visibility** - is a feature or a field *shown*? Hiding never deletes data and
never changes what anybody may do.
- **Permission** - may this person *do* it? Permissions are decided by roles, not
by what is shown.
A hidden feature is not a permission, and a permission does not make a hidden
feature appear.
## Visibility: is it shown?
From the widest layer to the narrowest. A narrower layer can only hide more; it can
never show what a wider one hides.
| Layer | Who sets it | Where | Decides |
| --- | --- | --- | --- |
| Instance features | Site admin | [Settings / Features](Settings/Features.md) | Which optional features (board view groups, helpers) exist on this WeKan at all. Pilot users still see the disabled ones. |
| Instance card fields | Site admin | [Settings / Features / Card fields](Settings/Features.md#card-fields) | Which card fields are shown on any board. |
| Feature profile | Site admin | [Settings / Feature profiles](Settings/Feature-Profiles.md) | Which of the instance's features chosen users, teams and organizations do not see. Opt-in: nobody without a profile is affected, and the user is told. |
| Board | Board admin | [Board Settings / Card](../Board-Sidebar/Board-Settings/Card.md) and [Board View](../Board-Sidebar/Board-Settings/Board-View.md) | Which fields this board shows on cards and minicards, and which views it offers. |
| Member | The user | [Member Settings](../Member-Settings/README.md) | Personal choices, for example hiding system messages. |
So a board view is in a user's Board View menu only when the instance offers it,
their feature profile (if any) does not hide it, and the board offers it.
## Permission: may they do it?
| Layer | Who sets it | Where | Decides |
| --- | --- | --- | --- |
| Admin Panel access | Site admin | [People / People](People/People.md) | Site administrators manage the whole instance; Organization administrators only their own organization's scope. |
| Board role | Board admin | [Members and Permissions](../Board-Sidebar/Members/Members.md), [Board roles](../Board-Sidebar/Members/Roles.md) | What a member may do on one board: Board admin, Normal, Read-only, Comment-only, Worker, Assigned-only and the rest. |
| List exception | Board admin | [List permissions](../Lists/List-Permissions.md) | For one list, a role may do more or less than the board allows. A refusing list also refuses bulk writes, rule actions, and deleting or moving the list or its swimlane. A board admin is never restricted. |
| Instance-wide role rules | Site admin | [People / Roles](People/Roles.md) | Which board roles may invite people to a board. |
| Organization and team rules | Site admin | [People / Organizations](People/Organizations.md), [People / Teams](People/Teams.md) | Shared templates, members propagated to boards, members synced from the identity provider, and adding members only from the same organization or team. |
| Server-wide switches | Site admin | [Settings / Security](Settings/Security.md), [Activities and notifications](Settings/Activities-and-Notifications.md), [Delete](Settings/Delete.md) | Import and export, rich text rendering, activity tracking, notifications and watching, permanent delete - for everybody. |
## When somebody says "it is missing"
1. **Their member menu** says *Your feature profile ... hides N features*? Then it
is their [feature profile](Settings/Feature-Profiles.md).
2. Missing for **everybody**? [Settings / Features](Settings/Features.md) has it
unticked.
3. Missing on **one board** only? The board's
[Board Settings](../Board-Sidebar/Board-Settings/README.md) do not show it.
4. **Shown but refused** when they use it? That is a permission: their
[board role](../Board-Sidebar/Members/Members.md) or a
[list exception](../Lists/List-Permissions.md).
+44
View File
@@ -0,0 +1,44 @@
# All Boards / Board labels
Above the board icons of All Boards is a **facet bar** (#4791): the boards you
see grouped by the first character of their names, by the organizations and
teams they are shared with, and by your own **board labels**, each group with
its count. Clicking a group shows only its boards; clicking it again, or
**Show all boards**, shows all of them again. The bar is drawn in the icon
view, not in the Table view (`.board-facets` in
`client/components/boards/boardsList.jade`).
## Board labels are your own
A board label is a name you file boards under. It is stored on your own user
document, `profile.boardLabels` as `{ label: [boardId, ...] }`, and is not
shown to anybody else; it does not change the board.
The label row (`fa-tag`) lists each of your labels that has at least one board
you can see, with its count:
- **Click the label** to show only its boards.
- **X** beside it (**Remove this board label**) calls `removeBoardLabel`,
which deletes that label from your profile. The boards are not changed.
## Apply label
At the end of the label row is a small form:
- **Board label** - the label's name, up to 40 characters; control
characters, `.` and `$` are removed.
- **for boards whose name includes** - the text to look for.
- **Apply label** - calls `applyBoardLabel` (`server/allBoardsFacets.js`).
Every board you see in All Boards whose name includes the text, ignoring case,
is added to that label; boards already under it stay. An empty name or text is
refused with an alert. The boards counted are the same ones All Boards lists:
not archived, not hidden by you, and visible to you through membership, an
organization, a team or an email domain. The grouping and matching are in
`models/lib/allBoardsFacets.js`.
## Related
- [All Boards](All-Boards.md)
- [Workspaces](Workspaces.md) - another way to file boards
- [Group members](Group-Members.md) - the organization and team tabs
+1 -1
View File
@@ -47,7 +47,7 @@ Archived boards are not deleted — you can restore them from the archive.
## Related
- [Board Background Images](../Board-Sidebar/Board-Settings/Background-Image.md)
- [Allow private boards only: Disable Public Boards](../Admin-Panel/Settings/Visibility.md)
- [Allow private boards only: Disable Public Boards](../Admin-Panel/Settings/Appearance.md)
- [Swimlanes](../Swimlanes/Swimlanes.md)
- [WIP Limits](../Lists/WipLimit/WipLimit.md)
- [Templates](Templates.md)
+41
View File
@@ -0,0 +1,41 @@
# All Boards / Organization and team tabs / Group members
Below the Workspaces in the All Boards left menu is one tab per organization
(`fa-sitemap`) and team (`fa-users`) you belong to (#802), listed from your
own user document (`myGroups()` in `models/lib/groupMembers.js`). With no
organizations or teams, there are no tabs.
Clicking a tab shows the boards shared with that group and, above them, its
members. Clicking the selected tab again goes back to all boards. The panel is
drawn in the icon view, not in the Table view.
## The members panel
The group's name, then each member's username and full name, with **(Admin)**
after the group's admins (`groupMembers` method, `server/groupMembers.js`, at
most 1000 members, sorted by username).
What you can do depends on `groupAccess()`:
| You are | You can |
| --- | --- |
| An admin of this organization or team, or a site admin | Add a member by username (**Add member**) and remove one (the **X**, *Remove from this group*). |
| A member of it | See who is in it. |
| Anybody else | Nothing: the server refuses. |
A group whose members come from the sign-in provider - LDAP or another
directory sync (`orgSyncMembersFromAuth` / `teamSyncMembersFromAuth`) - is
read-only for everybody, admins included, and says so: *Only this group's
admins can change who is in it. A group that comes from LDAP or another
directory is changed there, not in WeKan.* The same text is shown to a member
who is not an admin.
Adding an unknown username shows an error. Adding someone already in the group,
or removing someone not in it, changes nothing.
## Related
- [Admin Panel / People / Organizations](../Admin-Panel/People/Organizations.md)
- [Admin Panel / People / Teams](../Admin-Panel/People/Teams.md)
- [Board labels](Board-Labels.md) - the facet bar also groups boards by
organization and team
+30 -8
View File
@@ -38,15 +38,37 @@ table beside it.
| Menu name | Menu path | Description |
| --- | --- | --- |
| Settings | Admin Panel / Settings | **Version** (first, and the pane that opens with the Admin Panel), Visibility, Announcement, Accessibility, Translation, PWA, Global Webhooks. |
| People | Admin Panel / People | Login, E-mail, Domains, Organizations, Teams, People, Locked users, Roles, Shared templates. |
| Settings | Admin Panel / Settings | **Version** (first, and the pane that opens with the Admin Panel), Appearance, Features, Feature profiles, Security, Activities and notifications, Delete, Announcement, Accessibility, Translation, PWA, Global Webhooks, Shared labels. |
| People | Admin Panel / People | E-mail, Notifications, Domains, Organizations, Teams, People, Locked users, Audit log, Roles, Shared templates, Login, then the sign-in providers (SAML, LDAP, OAuth2, CAS, Header login, OAuth login providers, Passwordless login). |
| Attachments | Admin Panel / Attachments | The storage backends and the attachment/avatar tools. |
| Problems | Admin Panel / Problems | Summary, Security, Speed, Tests, CPU usage, then the reports — see [Table](../General/Table.md). |
| Problems | Admin Panel / Problems | Summary, Backup, then a **Reports** heading over the reports — see [Table](../General/Table.md). |
Four pages, not seven: **Translation** and **Version** became panes of Settings, and
**Features** was removed (its three panes are in Problems). A page whose menu had a
single entry was a page in name only — the entry belongs in the menu of the section
it is part of, and the tab that led to it is one tab fewer in the bar above.
Four pages, not seven: **Translation** and **Version** became panes of Settings,
and so did **Features**. Security, Activities and notifications and Delete, which
were settings listed in Problems, moved to Settings too, leaving Problems with
Summary, Backup and the reports. A page whose menu had a single entry was a page
in name only — the entry belongs in the menu of the section it is part of, and
the tab that led to it is one tab fewer in the bar above.
### All Boards
`client/components/boards/boardsList.jade` uses the same caret, grip, width and
pane title, with its own rows. From top to bottom:
| Menu entry | Guide |
| --- | --- |
| Starred and Remaining (Starred first when anything is starred, Remaining first when nothing is) | [All Boards](All-Boards.md), [Starred](../Pages/Starred.md) |
| Home | [Home](Home.md) |
| Templates | [Templates](Templates.md) |
| Share template with (under Templates, while it is selected) | [Share template with](Share-Template-With.md) |
| Archive | [Archive](Archive.md) |
| Workspaces | [Workspaces](Workspaces.md) |
| One tab per organization and team you are in | [Group members](Group-Members.md) |
| Teams / Organizations filter (when you are in any) | Filters the boards by the chosen teams and organizations |
The row order comes from `menuSectionOrder()` in `models/lib/allBoardsUrls.js`.
The facet bar above the boards, with your own board labels and **Apply
label**, is described in [Board labels](Board-Labels.md).
## Which side the menu is on
@@ -269,7 +291,7 @@ heading, and the page would print the same words a second time.
**Inside a pane, a group of settings may have its own title** —
`.admin-pane-group-title`, deliberately **smaller** than the pane title, with a
`<hr>` above it where a group needs separating from the one before. Admin Panel /
Settings / Visibility is the example: All Boards, URL, Product name, Logo. The
Settings / Appearance is the example: All Boards, URL, Product name, Logo. The
page then reads as one heading with groups under it, rather than as several pages
stacked.
+8
View File
@@ -6,13 +6,21 @@ be bookmarked. Open a board by its title. Access still follows board membership
and public/private visibility.
- [All Boards](All-Boards.md): overview, sorting and board actions
- [Left menu](Left-Menu.md): the rows of the menu, in order, and its design
- [Workspaces](Workspaces.md): workspace choices and roles
- [Home](Home.md): the board that opens after login
- [Public](Public.md): public boards and favorites
- [Starred](../Pages/Starred.md): starred boards and items
- [Page URLs](URLs.md): direct links and navigation
- [Archives](Archive.md): archived content
- [My Cards, Due Cards and My Attachments](../Pages/My-Cards-Due-Attachments.md)
- [Templates](Templates.md)
- [Share template with](Share-Template-With.md): drag a template board onto an
organization, team or email domain
- [Board labels](Board-Labels.md): the facet bar, your own board labels and
Apply label
- [Group members](Group-Members.md): the organization and team tabs and who is
in them
The signed-in Public page keeps favorite public boards in the user's profile,
so they remain selected after a reload. Starring does not grant private-board
@@ -0,0 +1,46 @@
# All Boards / Templates / Share template with
While **Templates** is the selected row of the All Boards left menu, a
**Share template with** heading appears directly under it, followed by one row
(`fa-share-alt`) per group a template board can be shared with
(`shareTargets` in `client/components/boards/boardsList.js`). Each row's
tooltip is *Drag a Template Board here to share it*. With no targets, neither
the heading nor rows are drawn.
## Which groups are offered
The server method `getMyShareableGroups` (`server/sharedTemplateTargets.js`)
returns, for the signed-in user:
- the **organizations** they belong to whose **Shared Templates** switch is on,
- the **teams** they belong to whose **Shared Templates** switch is on,
- the **email domains** of their own email addresses.
The page then keeps only the kinds - organizations, teams, domains - that are
ticked as scopes in Admin Panel / People / Shared templates. Those ticks are
read from this browser's `localStorage` (`sharedTemplatesScopes`), where that
pane stores them; a browser in which they were never set offers no targets.
## Sharing
Drag a template board's icon onto a row and drop it. Several selected boards
can be dropped at once with [Multi-Selection](../General/Multi-Selection.md);
boards dragged from the Archive are ignored. For each board the drop adds the
group to the board and never removes an existing share:
| Row | Method | Added to the board |
| --- | --- | --- |
| Organization | `setBoardOrgs` | `orgs`: `{ orgId, orgDisplayName, isActive: true }` |
| Team | `setBoardTeams` | `teams`: `{ teamId, teamDisplayName, isActive: true }`; members unchanged |
| Domain | `setBoardDomains` | `domains`: `{ domain, isActive: true }` |
A board that already has that group is left as it is. The server methods
require the user to be an **admin of the board** being shared, and only
teams the board admin belongs to may be added.
## Related
- [Templates](Templates.md)
- [Admin Panel / People / Shared templates](../Admin-Panel/People/Shared-Templates.md)
- [Organizations](../Admin-Panel/People/Organizations.md) and
[Teams](../Admin-Panel/People/Teams.md) - the Shared Templates switches
+20
View File
@@ -8,6 +8,26 @@ The chooser is drawn from `BOARD_VIEWS` in `models/lib/boardViewSettings.js`
board offers, and which one it opens in, is set in
[Board Settings / Board View](../Board-Sidebar/Board-Settings/Board-View.md).
## Header controls
The board's controls in the first header bar, in their order
(`boardHeaderButtons` in `client/components/boards/boardHeader.jade`). The
caret before them folds all of them away except the buttons a board's Rules
add; see [the header](../Header-Bar/Header.md).
| Control | Guide | Who can use it |
| --- | --- | --- |
| Visibility (Private / Signed-in users / Public) | [Visibility](Visibility.md) | Board admin; others see it disabled |
| Watch (Watching / Tracking / Muted) | [Watch](Watch.md) | Signed-in users; hidden when watching is disabled |
| Sort Cards | [Sort Cards](Sort-Cards.md) | Signed-in users |
| Filter | [Filter](../Board-Sidebar/Filter/README.md) | Signed-in users |
| Search | [Search](Search.md) | Signed-in users |
| Multi-Selection | [Multi-Selection](../General/Multi-Selection.md) | Users who can modify the board |
Signed out, the bar shows only a **Log in** button.
## More pages
- [Search](Search.md)
- [Board View Settings popup](Board-Views/Settings-Popup.md)
- [Board-view titles](Board-Views/Title-Rendering.md) and [activity rendering](Board-Views/Activity-Rendering.md)
+41
View File
@@ -0,0 +1,41 @@
# Board header / Sort Cards
The control after [Watch](Watch.md) in a board's header controls (`fa-sort`).
Its label and tooltip are **Sort Cards**, or **Sort is on** while a sort is
chosen; the button is then emphasised and an **X** beside it (**Remove
sort**) turns sorting off. See [the header](../Header-Bar/Header.md) for its
place in the bar.
Any signed-in user can use it. It changes only how the cards are shown to you:
it is stored in your browser (the `sortBy` Session value, saved to
`localStorage` as `wekan-cards-sortBy` so it survives a reload), not on the
board, and no card's position is changed.
## The popup
`cardsSortPopup` in `client/components/boards/boardHeader.jade`. Choosing an
entry sorts the cards inside each list and closes the popup.
| Entry | Order |
| --- | --- |
| Due Date | Earliest due date first (`dueAt: 1`). |
| Title (Alphabetically) | Title A to Z (`title: 1`). |
| Created At (Newest First) | Newest card first (`createdAt: -1`). |
| Created At (Oldest First) | Oldest card first (`createdAt: 1`). |
| Sort by votes | Highest vote score (positive minus negative) first. |
| Label order | By the board's label order: a card goes where its first label in that order goes, cards without a label last. |
The first four are passed to the card cursor as a sort, with the card `_id`
as a tie-breaker. **Sort by votes** and **Label order** are display orders
computed in `cardsWithLimit()` (`client/components/lists/listBody.js`) with
`models/lib/voteSortCards.js` and `models/lib/labelOrder.js`; cards with an
equal rank keep their manual order. The board's label order is changed by a
board admin with Move up / Move down when editing a label.
**Remove sort** clears the stored value, and the cards return to their manual
(dragged) order.
## Related
- [Filter](../Board-Sidebar/Filter/README.md)
- [Search](Search.md)
+63
View File
@@ -0,0 +1,63 @@
# Board header / Visibility
The first control of a board's header controls, after the fold caret: an icon
and the board's current visibility — **Private**, **Signed-in users** or
**Public**. The label and the tooltip are the same expression,
`{{_ currentBoard.permission}}`, so they always name the current setting. See
[the header](../Header-Bar/Header.md) for where the control sits and when its
label is hidden.
## Who can change it
Every signed-in user sees the button. Only a **board admin** gets the
`js-change-visibility` class that opens the popup; for everybody else the
button is drawn `is-disabled` and does nothing. The popup's choices are saved
with `Boards.updateAsync`, which the server allows only for a board admin.
## The popup
`boardChangeVisibilityPopup` in `client/components/boards/boardHeader.jade`.
Each row has an icon, the name, a check mark on the current choice, and a
description:
| Choice | Stored `permission` | Description |
| --- | --- | --- |
| Private (`fa-lock`) | `private` | Only people added to the board can view and edit it. |
| Signed-in users (`fa-users`) | `instance` | Every signed-in user of this WeKan can view the board; it is never shown to people who are not signed in. Only board members can edit. |
| Public (`fa-globe`) | `public` | Visible to anyone with the link, and can show up in search engines. Only board members can edit. |
Choosing a row calls `board.setVisibility()` and closes the popup.
- **Signed-in users** and **Public** are offered only while Admin Panel /
Settings / Appearance does not allow private boards only
(`tableVisibilityMode-allowPrivateOnly`). With that setting on, the popup
shows only Private, and a board that is already public or signed-in-users is
not displayed: the board page shows the `tableVisibilityMode-allowPrivateOnly`
text instead.
- The Private and Public descriptions can be replaced by an administrator in
[Admin Panel / Settings / Appearance](../Admin-Panel/Settings/Appearance.md)
(`customPrivateBoardDesc`, `customPublicBoardDesc`). Empty uses the default
text.
## Everyone signed in can edit
Below a rule, the popup offers one checkbox, **Everyone signed in can edit**,
when both are true:
- the board is **Signed-in users** or **Public**, and
- Admin Panel / Settings / Appearance allows it
(`tableVisibilityMode-allowInstanceEditing`).
Ticking it toggles the board's `allowsInstanceEditing`. Signed-in users who
are not members can then add, edit, move and comment on cards, and become
Normal members when they do.
The same visibility list, without this checkbox, is used in the Create Board
form (`createBoardForm`), where it sets the new board's visibility.
## Related
- [Admin Panel / Settings / Appearance](../Admin-Panel/Settings/Appearance.md)
- [Who sees what](../Admin-Panel/Who-Sees-What.md)
- [Public boards](../All-Boards/Public.md)
- [Board roles](../Board-Sidebar/Members/Roles.md)
+54
View File
@@ -0,0 +1,54 @@
# Board header / Watch
The control after [Visibility](Visibility.md) in a board's header controls. It
shows your own watch level for this board — **Watching** (`fa-eye`),
**Tracking** (`fa-bell`) or **Muted** (`fa-bell-slash`) — as its icon, label
and tooltip. See [the header](../Header-Bar/Header.md) for its place in the bar.
The level is per user: it is stored in the board's `watchers` array as
`{ userId, level }` (`models/watchable.js`). A user with no entry is
**Muted**, which is the default; choosing Muted removes the entry.
## Who can use it
Every signed-in user who can see the board. The button is not drawn when an
administrator has turned on **Disable watch** in
[Admin Panel / Settings / Activities and notifications](../Admin-Panel/Settings/Activities-and-Notifications.md)
(`watchDisabled` helper, `Settings.disableWatch`).
## The popup
`boardChangeWatchPopup` in `client/components/boards/boardHeader.jade`. The
current level has a check mark.
| Level | Description shown |
| --- | --- |
| Watching | You will be notified of any change in this board. |
| Tracking | You will be notified of changes to the cards you are involved in as creator or member. |
| Muted | You will never be notified of any changes in this board. |
Choosing a row calls the `watch` method (`server/notifications/watch.js`) with
`'board'`, the board id and the level, and closes the popup when it succeeds.
The server refuses, and the popup says why in an alert, when:
- watching is disabled by the administrator (`error-watch-disabled`), or
- the user may not see the board (`error-board-notAMember`). Seeing it through
membership, an organization, a team, an email domain, or because it is
public or signed-in-users all count.
## What the level does
In `server/models/activities.js`, an activity on the board notifies users at
**Watching** for every activity, and users at **Tracking** only for activities
they are a participant in. `models/lib/boardNotificationRecipients.js` then
keeps only active board members whose level is Watching or Tracking, or who
explicitly watch the list or card concerned. Being assigned or mentioned does
not reach a member who has muted the board.
How a notification is delivered (in-app, email, ntfy and so on) is chosen in
[Member Settings / Notifications](../Member-Settings/Notifications.md) and
[Board Settings / Notifications](../Board-Sidebar/Board-Settings/Notifications.md).
## Related
- [Notification delivery](../General/Notifications/Notification-Delivery.md)
@@ -0,0 +1,33 @@
# Board Settings / All Boards Settings
**All Boards Settings** (i18n key `board-info-on-my-boards`) is the popup
`boardInfoOnMyBoardsPopup` in `client/components/sidebar/sidebar.jade`, with
its helpers and events in `client/components/sidebar/sidebar.js`.
**It is not in the Board Settings menu at the moment.** The menu entry that
opens it (`a.js-board-info-on-my-boards`, `fa-id-card-o`) is commented out in
`boardMenuPopup`, with the note *Bug Board icons random dance* (#4214). The
popup and its click handler (`'click .js-board-info-on-my-boards'`) are still
in the code, so this page describes what it does when opened.
## The popup
Under the heading **Show at All Boards page**, each row saves at once to the
current board with `Boards.updateAsync`, which the server allows for a board
admin:
| Row | Board field | What it does |
| --- | --- | --- |
| Show card count per list | `allowsCardCounterList` | The board's tile on All Boards shows the card count of each list. Not drawn when an administrator hides card counters (`Settings.hideCardCounterList`). |
| Card aging (fade old cards) | `cardAging` | Minicards fade in three steps the longer they go without activity. While on, three day fields set the steps (`cardAgingDays1/2/3`, default 7, 14 and 28 days). |
| Archive cards after this many days without activity | `autoArchiveInactiveDays` | Checked every hour by `server/autoArchiveCards.js`. A card counts as active whenever it is changed; templates are never archived. Empty turns it off. |
| Show Board members avatars | `allowsBoardMemberList` | The board's tile on All Boards shows its members' avatars. Not drawn when an administrator hides member lists (`Settings.hideBoardMemberList`). |
| Personal list widths | `allowsPersonalListWidth` | On: each user keeps their own list widths. Off: list widths are shared with everyone on the board. |
The two administrator switches are in the **All Boards: Hide** group of
[Admin Panel / Settings / Appearance](../../Admin-Panel/Settings/Appearance.md).
## Related
- [All Boards](../../All-Boards/All-Boards.md)
- [List settings](List.md)
@@ -0,0 +1,31 @@
# Board Settings / Board announcement
**Right sidebar / Board Settings / Board announcement** (`fa-bullhorn`), after
**Change Color**, is the board's own announcement (#1566), in the style of the
site-wide [Admin Panel announcement](../../Admin-Panel/Settings/Announcement.md)
but one per board. Shown to **board admins only**; saving goes through
`Boards.updateAsync`, which the server allows for a board admin.
## The popup
`boardAnnouncementPopup` in `client/components/boards/boardAnnouncement.jade`:
- **Board announcement** - the text, up to 2000 characters, plain text (it is
escaped when shown).
- **Show it to everyone on this board** - the on/off checkbox.
- **Save** - stores `announcement: { enabled, body, updatedAt }` on the board
(`cleanBoardAnnouncement()` in `models/lib/boardAnnouncement.js`). The text is
trimmed; empty text saves the announcement as not enabled.
## What members see
Above the board's lists (`boardAnnouncement` in `boardBody.jade`), a bar with
the bullhorn, the text and a close **X**, shown while the announcement is
enabled and not empty. The **X** calls `dismissBoardAnnouncement`, which records
in the user's profile the version (the `updatedAt` time) they dismissed. Every
save sets a new version, so an edited announcement is shown again to everyone,
including those who dismissed the earlier one.
## Related
- [Admin Panel / Settings / Announcement](../../Admin-Panel/Settings/Announcement.md)
@@ -0,0 +1,17 @@
# Board Settings / Bots
**Right sidebar / Board Settings / Bots** (`fa-android`) is the third of the
Rules entries, after **List view** and **Workflow view**. It opens the board's
Rules page in its **Bots** view (`openRulesViewFromBoardMenu('bots')` in
`client/components/sidebar/sidebar.js`): runners on your own server that this
board hands cards to.
Like every entry of the Rules group it is shown to **board admins only**. It
is not a board view, so it is not in the Board View menu.
What the view shows and how a bot is added, run and answered is described in
[Rules / Bots](../../Rules/Bots.md).
## Related
- [Automation rules](../../Rules/Rules/Rules.md)
@@ -0,0 +1,24 @@
# Board Settings / Change Color
**Right sidebar / Board Settings / Change Color** (`fa-paint-brush`) opens
`boardChangeColorPopup` (`client/components/sidebar/sidebar.jade`), the
board's own colour. It is in the group after **Scrum settings**, and like the
rest of that group it is shown to **board admins only**.
The popup is the shared colour picker, `themeColorPicker` with
`scope="board"`: the themes as swatches grouped by category, with a check mark
on the current one, and for the flat and clear categories the custom-colour
wheels and a preview. A click applies at once - there is no Save - by calling
`board.setColor()`, which stores `color` and, when they are valid for that
category, `customThemeColors` on the board. A board always has a colour, so
this scope has no "Default theme" row.
The board colour owns the board page: the site theme is not applied there, but
a user's own Member Settings colour is. The picker, its categories and the
order of themes are described once in
[Change color](../../General/Theme/Change-Color.md).
## Related
- [Theme](../../General/Theme/Theme.md)
- [Change Background Image](Background-Image.md)
@@ -1,29 +1,44 @@
# Right sidebar / Board Settings
Open a board's right sidebar, then **Board Settings**. The entries appear in
this order; permissions and site policy can hide individual entries.
Open a board's right sidebar, then **Board Settings** (`boardMenuPopup` in
`client/components/sidebar/sidebar.jade`). The entries appear in this order,
in groups divided by a rule; permissions and site policy can hide individual
entries.
| Entry | Guide or action | Who can change it |
| --- | --- | --- |
| Rules | [Automation rules](../../Rules/Rules/Rules.md) | Board admin |
| List View, Workflow, Blocks, History | The Rules page opened in that view | Board admin |
| Rules | [Automation rules](../../Rules/Rules/Rules.md) | Board admin; a member reads them where the board shows its Rules |
| List view, Workflow view | The Rules page opened in that view | Board admin |
| Bots | [The Rules page's Bots view](Bots.md) | Board admin |
| Blocks, History | The Rules page opened in that view | Board admin |
| Import / Export rules | Rules import and export, opened here | Board admin |
| Change Color | Board background color | Board admin |
| Scrum settings | [Planning settings in the Sprints view](Scrum-Settings.md) | Board admin |
| Change Color | [The board's colour](Change-Color.md) | Board admin |
| Board announcement | [A message shown to everyone on the board](Board-Announcement.md) | Board admin |
| Change Background Image | [Upload and choose a background](Background-Image.md) | Board admin |
| Date | [Board date override and week numbers](Date.md) | Board admin for the format |
| Board View | [Visible views, defaults and menu order](Board-View.md) | Board admin |
| Swimlane | [Height resize lock and WIP Limit Groups](Swimlane.md) | Board admin |
| Date | [Board date override and week numbers](Date.md) | Board admin for the format |
| List | [Width resize lock and same width for all lists](List.md) | Board admin |
| Card | [Field visibility and order](Card.md) | Board admin; personal Labels text remains available to members |
| Export | [Export board content](Import-Export.md) | Export must be enabled |
| Import | [Import into the board](Import-Export.md) | Write access; import must be enabled |
| Notifications | [Board delivery defaults](Notifications.md) | Board admin |
| Outgoing Webhooks | [Send events to integrations](Outgoing-Webhooks/Discord/Outgoing-Webhook-to-Discord.md) | Board admin |
| Archived Items | [Review and restore archives](../Archive/Archive-and-Delete.md) | Actions depend on role |
| Archive | [Review and restore archives](../Archive/Archive-and-Delete.md) | Actions depend on role |
| Original positions | [Where swimlanes, lists and cards were made, and what moved](../../General/Original-Positions/Original-Positions.md) | Everyone who can see the board |
| Summary | [The board at a glance](../../General/Summary/Summary.md) | Everyone who can see the board; hidden by its switch in Admin Panel / Settings / Features |
| Since your last visit | [What changed since you were here](../../General/Since-Last-Visit/Since-Last-Visit.md) | Everyone who can see the board; hidden by its switch in Admin Panel / Settings / Features |
| Save as Template | [Copy the board into your board templates](../../All-Boards/Templates.md#d-save-an-existing-board-as-a-board-template) | Board admin; not on a template board |
| Move Board to Archive | [Archive the board](../Archive/Archive-and-Delete.md) | Board admin; unavailable on the templates board |
Rules and its five views form the first group; a divider separates them from
Change Color and the rest of the board's look.
The groups are: Rules and its views; Scrum settings; Change Color to Date (the
board's look); Board View to Card; Export to Outgoing Webhooks; and Archive to
Move Board to Archive.
[All Boards Settings](All-Boards-Settings.md) (what the board's tile shows on
All Boards, card aging, auto-archive and personal list widths) has a popup in
the code, but its menu entry is commented out and not shown.
Custom Fields are reached from an opened card's menu, then the settings cog.
Subtasks settings are behind the menu beside an opened card's **Subtasks**
@@ -0,0 +1,47 @@
# Board Settings / Scrum settings
**Right sidebar / Board Settings / Scrum settings** (`fa-repeat`) is a group of
its own, between the Rules group and **Change Color**. Shown to **board admins
only**. It does not open a popup: it switches the board to the **Sprints** view
and opens that view's **Scrum settings** section
(`Session.set('scrumOpenSettings', true)` and
`Utils.setBoardView('board-view-sprints')` in
`client/components/sidebar/sidebar.js`).
## The settings
`details.scrum-settings` in `client/components/boards/scrum/scrumView.jade`,
drawn when the server says the user is a board admin (`canAdmin`):
| Field | What it sets |
| --- | --- |
| Enable Scrum planning | Whether Scrum planning is on for this board. |
| Product Goal | Free text. |
| Definition of Done | Free text. |
| Product Owner | One active board member, or none. |
| Scrum Master | One active board member, or none. |
| Developers | Any number of active board members. |
| Working days | One or more of Monday to Sunday (required). |
| Estimate source | **Planning poker estimate** or **Numeric custom field**. |
| Custom Fields | The custom field to read estimates from, or none. |
| Estimate unit | Free text, up to 80 characters. |
| Completion policy | A card counts as done when it is **marked complete**, or when it is **in a Done-category list**. |
**Save** calls `scrum.configure` (`server/scrum.js`), which checks again that
the caller is a board admin and stores the settings in the board's `scrum`
field with a revision number; a save based on an older revision is refused as a
conflict. The estimate source, estimate field, estimate unit and completion
policy cannot be changed while a sprint is active.
Below it, **Import Scrum planning into this board** takes a WeKan board export
or a Scrum transfer file, previews what would change, and imports on
confirmation (`scrum.importIntoBoard`, board admins only). Existing sprints and
releases are linked rather than duplicated; cards are matched by ID, or by card
number and title, and unmatched cards are listed and left unchanged.
## Related
- [Sprints](../../Board-Header/Board-Views/Scrum/Sprints.md)
- [Product Backlog](../../Board-Header/Board-Views/Scrum/Product-Backlog.md)
- [Sprint reports and velocity](../../Board-Header/Board-Views/Scrum/Sprint-Reports.md)
- [Scrum design](../../Board-Header/Board-Views/Scrum/Scrum-Design.md)
+4
View File
@@ -108,6 +108,10 @@ back when it was moved back. The startup schema upgrade (step
`card-children-boardid`) moves rows that were left behind to their card's current
board, once per new WeKan version.
The card menu's own entries are described in
[Card menu / Move Card](Move-Card.md) and
[Card menu / Copy Card](Copy-Card.md).
## Filtered views
Filter the board by member, label, due date, and more to focus on a subset of cards.
+38
View File
@@ -0,0 +1,38 @@
# Card menu / Copy Card
Card menu (☰ in the opened card's header, **Card Actions**) → **Copy Card**
makes a copy of the card on this board or another one (`copyCardPopup` in
`client/components/cards/cardDetails.jade`).
## Who sees it
A user to whom the menu offers its moving and copying entries (helper
`cardMenuWrites`: somebody who may change the card, or a member who is not
**Read only** or **Read assigned only**), and who is not a **Worker**.
## The popup
| Field | What it does |
| --- | --- |
| **Title** | the copy's title, prefilled with the card's; an empty title copies nothing |
| **Boards**, **Swimlanes**, **Lists** | the destination, as in [Move Card](Move-Card.md) |
| **Cards**, **Above selected card** / **Below selected card** | where the copy goes; with no card chosen it goes to the bottom |
| **Done** | copies |
The destination is remembered per board, as for Move Card. If the board is
filtered, the copy is added to the filter's exceptions so it does not vanish
at once ([#80](https://github.com/wekan/wekan/issues/80)).
## Server checks
The copy is made by the `copyCard` server method (`server/models/cards.js`).
It refuses when you are not signed in, not a member of the source board, an
assigned-only member copying a card not assigned to you, without write
access to the destination board, or when the destination list's
[permission](../Lists/List-Permissions.md) refuses your role. On another
board, labels are matched by name.
## Related
- [Copy Template to Many Cards](Copy-Template-To-Many-Cards.md)
- [Save as Template](../All-Boards/Templates.md)
@@ -0,0 +1,37 @@
# Card menu / Copy Template to Many Cards
Card menu (☰ in the opened card's header, **Card Actions**) → **Copy
Template to Many Cards** makes several copies of this card at once, each
with its own title and description (`copyManyCardsPopup` in
`client/components/cards/cardDetails.jade`).
## Who sees it
The same users as [Copy Card](Copy-Card.md): the menu offers its moving and
copying entries to them (`cardMenuWrites`), and they are not a **Worker**.
## The popup
The text box, labelled **Destination Card Titles and Descriptions in this
JSON format**, is prefilled with an example:
```json
[ {"title": "First card title", "description":"First card description"},
{"title":"Second card title","description":"Second card description"},
{"title":"Last card title","description":"Last card description"} ]
```
Replace it with one object per card to create. Below it is the same
destination picker as [Move Card](Move-Card.md): board, swimlane, list,
a card and **Above selected card** / **Below selected card**, and **Done**.
## What happens
- The text is parsed as JSON. Text that is not valid JSON creates nothing,
and the error is shown in the popup.
- For each object, the `copyCard` server method copies this card with the
object's `title` and `description` (with the same checks as Copy Card),
then places it. With **Below selected card**, each copy goes below the
previous one, so they keep the order of the text.
- With no card chosen, each copy goes to the bottom of the list.
- On a filtered board, each copy is added to the filter's exceptions.
@@ -0,0 +1,41 @@
# Card menu / Create board from this card
Turns the card into a link to a **new board**: WeKan creates a board, and the card
becomes a linked-board card that opens it. The card itself is converted, not
copied - its title stays, and nothing else on it changes.
## Using it
1. Open the card, then its hamburger menu.
2. **Create board from this card** opens a popup with the new board's **name**,
filled in with the card's title.
3. Press **Create board from this card**. The new board is created with you as
its admin and a default swimlane, and the card now opens that board.
If the server refuses, the reason is shown and nothing changes.
## Who sees it
The entry is drawn only when:
- board creation is allowed for you (Admin Panel / People / Login can let only
admins create boards - [CreateBleed](https://wekan.fi/hall-of-fame/createbleed/)),
and
- the menu's write section is shown to you and you are not a Worker.
In the current template the entry also sits under `unless canModifyCard`, so a
member who can edit the card does not see it - see TODO.md.
## What the server checks
`createBoardFromCard` (`server/models/cards.js`): the card exists, is not
archived and is not already a link or a template; you may write on its board; an
assigned-only member converts only a card assigned to them; the card's list does
not refuse your role ([List permissions](../Lists/List-Permissions.md)); and you
may create boards. The new board is private unless the source board is open, and
always private when the instance allows private boards only.
## Related
- [Link to board](Link-To-Board.md) - link a card to an EXISTING board.
- [Card menu](README.md)
+28
View File
@@ -0,0 +1,28 @@
# Card menu / Link to board
Card menu (☰ in the opened card's header, **Card Actions**) → **Link to
board** puts a [linked card](Linked-Cards.md) of this card on another,
existing board ([#4281](https://github.com/wekan/wekan/issues/4281);
`linkCardToBoardPopup` in `client/components/cards/cardDetails.jade`).
## Who sees it
Somebody who may change the card (`canModifyCard`) and is not a **Worker**.
## The popup
The same destination picker as [Move Card](Move-Card.md): **Boards**,
**Swimlanes**, **Lists**, **Cards** with **Above selected card** /
**Below selected card**, and **Done**. With no card chosen, the linked card
goes to the bottom of the list. The destination is remembered per board.
## What it creates
A new card of type `cardType-linkedCard` whose `linkedId` points to the
original card (`link` in `models/cards.js`). Its labels are not copied, and
only custom-field values of fields that belong to the destination board are
kept. The original card is not changed. On a filtered board the new card is
added to the filter's exceptions.
The same link is what [Move Card](Move-Card.md)'s **Leave a link at the
original location** leaves behind.
+33
View File
@@ -0,0 +1,33 @@
# Card menu / More
Card menu (☰ in the opened card's header, **Card Actions**) → **More**
opens a popup with the card's link, its parent cards and its creation date
(`cardMorePopup` in `client/components/cards/cardDetails.jade`).
## Who sees it
A user to whom the menu offers its moving and copying entries (helper
`cardMenuWrites`), who is not a **Worker**.
## What it shows
| Part | What it does |
| --- | --- |
| **Link to this card** | the board's visibility icon and a read-only box with the card's address |
| **Copy card link to clipboard** | copies that address; inside Sandstorm it opens Sandstorm's sharing instead ([#1188](https://github.com/wekan/wekan/issues/1188)) |
| **Change card's parent**: **Source board**, **Parent card** | makes the card a subtask of a card on one of your boards, or of none; this is the primary parent |
| **Also a subtask of** | the other parent cards, each with × to remove it ([#3626](https://github.com/wekan/wekan/issues/3626)) |
| **Add another parent card** | adds a further parent from the chosen board |
| **Added** | the date the card was created |
| **Delete** | board admins only; permanent, after a confirmation |
The parent-card list is filled once the chosen board's cards have loaded
([#3745](https://github.com/wekan/wekan/issues/3745),
[#6917](https://github.com/wekan/wekan/issues/6917)). See
[Subtasks](Subtasks.md).
**Delete** removes the card only when no linked card elsewhere points to it;
otherwise it says *You can not delete this card before first deleting linked
card that has* and the card stays. To keep a card restorable, use **Move
Card to Archive** instead
([Archive and Delete](../Board-Sidebar/Archive/Archive-and-Delete.md)).
+40
View File
@@ -0,0 +1,40 @@
# Card menu / Move Card
Card menu (☰ in the opened card's header, **Card Actions**) → **Move Card**
moves the card to another place on this board or to another board
(`moveCardPopup` in `client/components/cards/cardDetails.jade`).
## Who sees it
Only a **board admin**, and only when the menu's moving and copying entries
are offered at all (helper `cardMenuWrites`): to somebody who may change the
card, or to a member who is not **Read only** or **Read assigned only**.
## The popup
| Field | What it does |
| --- | --- |
| **Title** | the card's title; a changed title is saved after the move |
| **Move reason (optional)** | up to 1000 characters, passed with the move |
| **Boards** | the active boards you are an active member of, without your Templates board |
| **Swimlanes**, **Lists** | the destination swimlane and list on that board |
| **Cards**, **Above selected card** / **Below selected card** | where in the list the card goes; with no card chosen it goes to the bottom |
| **Leave a link at the original location** | off by default; when on, a [linked card](Linked-Cards.md) is left where the card was ([#2719](https://github.com/wekan/wekan/issues/2719)) |
| **Done** | moves; disabled until the destination's cards have loaded |
The destination you choose is remembered per board in your profile
(`profile.moveAndCopyDialog`) and offered next time. The same destination
picker (`cardDestinationPicker`) is used by
[Copy Card](Copy-Card.md),
[Copy Template to Many Cards](Copy-Template-To-Many-Cards.md) and
[Link to board](Link-To-Board.md).
## What moves along
A card moved to another board takes its comments, reactions, text note,
checklists and attachments along; see
[Moving a card to another board](Cards.md#moving-a-card-to-another-board).
A [list permission](../Lists/List-Permissions.md) that refuses your role in
the source or the destination list refuses the move. An error is shown in
the popup.
+22
View File
@@ -0,0 +1,22 @@
# Card menu / Move to Top, Move to Bottom
Card menu (☰ in the opened card's header, **Card Actions**) → **Move to
Top** and **Move to Bottom** move the card to the first or last place of its
own list, in its own swimlane.
## Who sees them
A user to whom the menu offers its moving and copying entries (helper
`cardMenuWrites`: somebody who may change the card, or a member who is not
**Read only** or **Read assigned only**). Workers see them too.
## What happens
- **Move to Top** gives the card a sort number one below the lowest of the
non-archived cards in the same list and swimlane.
- **Move to Bottom** gives it one above the highest.
- The card stays on the same board, swimlane and list (`card.move`); only
its order changes. The menu then goes back.
The server still decides whether the move is allowed, including a
[list permission](../Lists/List-Permissions.md) of the card's list.
+24
View File
@@ -0,0 +1,24 @@
# Card menu / QR code
Card menu (☰ in the opened card's header, **Card Actions**) → **QR code**
shows the card's link as a QR code, to open the card on a phone or tablet
([#2015](https://github.com/wekan/wekan/issues/2015); `cardQrCodePopup` in
`client/components/cards/cardDetails.jade`).
## Who sees it
Every signed-in user who can open the card. It changes nothing.
## What it shows
- The QR code of the card's absolute address (the same one **Copy link to
clipboard** copies; see [Board item links](../General/Board-Item-Links.md)),
264 × 264 pixels.
- *Scan it to open this card on a phone or tablet.* and the address as text.
- If the address is too long for the encoder: *The link of this card is too
long for a QR code.*
The code is drawn in the browser by `models/lib/qrCode.js` (byte mode, error
correction level M, versions 1-10, up to 213 bytes). Nothing is sent
anywhere. Whoever scans it still has to sign in and have access to the
board.
+27
View File
@@ -36,3 +36,30 @@ opened card and on the minicard, is [Card Settings](Card-Settings.md) -
The opened-card heading is **Date**, not Change Date Format. Linked-card titles
navigate within the same tab; use the browser's link controls when you want a
separate tab.
## Card menu
Card menu (☰ in the opened card's header, **Card Actions**), in menu order
(`cardDetailsActionsPopup` in `client/components/cards/cardDetails.jade`).
Who sees which entry is on each page.
| Entry | Guide |
| --- | --- |
| Move Card | [Move Card](Move-Card.md) |
| Copy Card | [Copy Card](Copy-Card.md) |
| Save as Template | [Templates](../All-Boards/Templates.md) |
| Copy Template to Many Cards | [Copy Template to Many Cards](Copy-Template-To-Many-Cards.md) |
| Card recurrence | [Card recurrence](Card-Recurrence.md) |
| Move to Top, Move to Bottom | [Move to Top / Bottom](Move-To-Top-Bottom.md) |
| Watch / Unwatch, Star / Unstar | [Watch, Star](Watch-Star.md) |
| Set color | [Set color](Set-Color.md) |
| Drawing | [Drawing](Drawing.md) |
| Create cards from action items | [Action items](Action-Items.md) |
| Copy link to clipboard | [Board item links](../General/Board-Item-Links.md) |
| Link to board | [Link to board](Link-To-Board.md) |
| QR code | [QR code](QR-Code.md) |
| History | [History](../General/History/History.md) |
| Export, Import | [Scope, formats and limits](../Board-Sidebar/Board-Settings/Import-Export/Format-Coverage.md) |
| Move Card to Archive / Restore | [Archive and Delete](../Board-Sidebar/Archive/Archive-and-Delete.md) |
| More | [More](More.md) |
| Create board from this card | [Create-Board-From-Card.md](Create-Board-From-Card.md) |
+35
View File
@@ -0,0 +1,35 @@
# Card menu / Set color
Card menu (☰ in the opened card's header, **Card Actions**) → **Set color**
opens the card's colour popup (`setCardColorPopup` in
`client/components/cards/cardDetails.jade`).
## Who sees it
Somebody who may change the card (`canModifyCard`, which includes the
card's [list permission](../Lists/List-Permissions.md)), and who is not a
**Worker**.
## The popup
| Control | What it does |
| --- | --- |
| Palette | the named colours (`ALLOWED_COLORS`) except white; the current one has a check mark |
| Custom swatches | the custom `#rrggbb` colours already used by cards of this board |
| **Custom color** | the browser's colour wheel ([#5514](https://github.com/wekan/wekan/issues/5514)) |
| **Save** | saves the chosen colour on the card |
| **Remove** | removes the card's colour |
## Where it shows
- On the minicard and in the opened card's header, unless **Card color** is
turned off for that place in
[Board Settings / Card](../Board-Sidebar/Board-Settings/Card.md)
(`allowsCardColorOnMinicard`, `allowsCardColorOnCard`).
A card without a colour of its own can be shown in its list's colour; see
[List menu / Set Color](../Lists/Set-Color.md). The card's own colour always
wins.
Several cards can be coloured at once from
[Multi-Selection](../General/Multi-Selection.md).
+29
View File
@@ -0,0 +1,29 @@
# Card menu / Watch, Star
Card menu (☰ in the opened card's header, **Card Actions**) has two
per-user toggles: **Watch** / **Unwatch** and **Star** / **Unstar**. Every
signed-in user who can open the menu sees both.
## Watch
- **Watch** sets your watch level on the card to *watching*, **Unwatch**
removes it (the `watch` server method, `server/notifications/watch.js`).
On a linked card it is the original card that is watched.
- Watchers of a card receive notifications of its activities.
- When **Disable watch** is on in
[Admin Panel / Settings / Activities and notifications](../Admin-Panel/Settings/Activities-and-Notifications.md),
the server refuses every change of a watch level.
## Star
- **Star** bookmarks the card for you
([#1172](https://github.com/wekan/wekan/issues/1172)): its id is added to
or removed from your `profile.starredCards` by the `toggleCardStar` server
method (`server/models/users.js`). Nobody else sees it, and the card is not
changed.
- Starred cards appear in the header's bookmarks dropdown (the five most
recently starred) and on the **Starred** page (`/starred-items`), where a
starred card opens in place. See [Starred](../Pages/Starred.md).
The same Star entry exists in the [list menu](../Lists/Star.md) and the
[swimlane menu](../Swimlanes/Star.md).
@@ -12,15 +12,15 @@ explained by the rule that produced it.
| --- | --- | --- | --- | --- |
| 1 | A due date from the card title | Add card, card title | [Due date from the title](../../Cards/Dates/Due-Date-From-Title.md) | Board Settings / Card: **Due date from title** |
| 2 | Similar cards and possible duplicates | Add card, opened card | [Similar cards](../../Cards/Similar-Cards.md) | Board Settings / Card: **Similar cards** |
| 3 | Rule suggestions | Board menu → Rules | [Rule suggestions](../../Rules/Rule-Suggestions.md) | Admin Panel / Settings / Visibility / Features: **Rule suggestions** |
| 4 | Summary (standup) | Board menu → Summary | [Summary](../Summary/Summary.md) | Admin Panel / Settings / Visibility / Features: **Summary** |
| 5 | Since your last visit | Board menu → Since your last visit | [Since your last visit](../Since-Last-Visit/Since-Last-Visit.md) | Admin Panel / Settings / Visibility / Features: **Since your last visit** |
| 3 | Rule suggestions | Board menu → Rules | [Rule suggestions](../../Rules/Rule-Suggestions.md) | Admin Panel / Settings / Features: **Rule suggestions** |
| 4 | Summary (standup) | Board menu → Summary | [Summary](../Summary/Summary.md) | Admin Panel / Settings / Features: **Summary** |
| 5 | Since your last visit | Board menu → Since your last visit | [Since your last visit](../Since-Last-Visit/Since-Last-Visit.md) | Admin Panel / Settings / Features: **Since your last visit** |
| 6 | At risk | Minicard, opened card | [At risk](../../Cards/At-Risk.md) | Board Settings / Card: **At risk** |
| 7 | Suggested members | Members and Assignees popups | [Suggested members](../../Cards/Suggested-Members.md) | Board Settings / Card: **Suggested members** |
| 8 | Forecast done date | Opened card's dates, minicard | [Forecast](../../Cards/Dates/Forecast.md) | Board Settings / Card: **Forecast** |
| 9 | Checklist or subtasks from the description | Opened card, Checklists | [Checklist from description](../../Cards/Checklist-From-Description.md) | Board Settings / Card: **Checklist from description** |
| 10 | Action items from a comment or description | Opened card, comment menu | [Action items](../../Cards/Action-Items.md) | Board Settings / Card: **Action items** |
| 11 | Search phrases in plain language | Global search | [Search phrases](../../Pages/Search-Phrases.md) | Admin Panel / Settings / Visibility / Features: **Search phrases** |
| 11 | Search phrases in plain language | Global search | [Search phrases](../../Pages/Search-Phrases.md) | Admin Panel / Settings / Features: **Search phrases** |
## Hiding them
@@ -30,10 +30,10 @@ They are hidden the way every other optional part of WeKan is:
[Board Settings / Card](../../Board-Sidebar/Board-Settings/Card.md), so a
board admin turns each one off for the opened card, the minicard, or both.
The same rows are ticks in
[Admin Panel / Settings / Visibility / Features / Card fields](../../Admin-Panel/Settings/Visibility.md#card-fields),
[Admin Panel / Settings / Features / Card fields](../../Admin-Panel/Settings/Features.md#card-fields),
where a site admin hides them on every board at once.
- **The board and search helpers (3, 4, 5, 11)** are features of
[Admin Panel / Settings / Visibility / Features](../../Admin-Panel/Settings/Visibility.md#features):
[Admin Panel / Settings / Features](../../Admin-Panel/Settings/Features.md#features):
untick one and its menu entry, its panel and its server answers are gone for
everyone except the previewers named there.
+2 -2
View File
@@ -118,7 +118,7 @@ Each service's own categories become WeKan's:
- a spam report is a **complaint**.
A request with a wrong or missing signature or password is refused (HTTP 401)
and shows in Admin Panel → Problems → Security. A service that is turned off
and shows in Admin Panel → Problems → Security Report. A service that is turned off
answers 404. Keys and passwords are written only when typed, and are never sent
back to a browser.
@@ -155,7 +155,7 @@ Problems → Email**:
- an email that could not be read;
- an email for a board that no longer takes email.
Attempts are listed in Problems → Security instead: a guessed board address, a
Attempts are listed in Problems → Security Report instead: a guessed board address, a
wrong webhook secret, a forged SNS message.
## Files
+3 -3
View File
@@ -85,7 +85,7 @@ time, provenance or chain link invalidates the row.
Before restore, undo or redo applies content, the server verifies the selected row
and its chain link. A mismatch refuses the operation, records
`history-integrity-failed` in Problems → Security and Recovery, and schedules a
`history-integrity-failed` in Problems → Security Report and Recovery, and schedules a
low-load full-chain audit. It never attempts to infer or silently repair historical
content. Concurrent appenders serialize the per-board chain head so two valid rows
cannot claim the same predecessor unnoticed.
@@ -534,9 +534,9 @@ Decided (maintainer, 2026-09). These are rules, not proposals; the tests under
and the CollectionFS export in `attachmentBulkMove.js` converts a storage format and keeps
the file. A source-reading test lists these and fails on any other.
### 12.4 The only hard delete: Admin Panel / Problems / Delete → archive → delete
### 12.4 The only hard delete: Admin Panel / Settings / Delete → archive → delete
- With **Enable permanent delete** on (Admin Panel / Problems / Delete, `enablePermanentDelete`),
- With **Enable permanent delete** on (Admin Panel / Settings / Delete, `enablePermanentDelete`),
a global admin can archive a board and then delete it from the archive
(`permanentlyDeleteArchivedBoards`). Removing the board removes **every attachment whose
`meta.boardId` is that board — live and soft-deleted alike — and their files** from the
@@ -18,7 +18,7 @@ A board you have never opened shows its last seven days.
## Hiding it
Admin Panel / Settings / Visibility / Features: **Since your last visit**. The
Admin Panel / Settings / Features: **Since your last visit**. The
visit times are still kept while it is hidden, so turning it on again shows the
right changes.
+1 -1
View File
@@ -24,7 +24,7 @@ there. Cards the reader may not see are left out.
## Hiding it
Admin Panel / Settings / Visibility / Features: **Summary**.
Admin Panel / Settings / Features: **Summary**.
## Implementation
Loaded 100 of 574 files, more files were not shown because too many files have changed in this diff. Show more