Leantime vs MeisterTask
Side-by-side trajectory, velocity, and editorial themes.
Leantime swaps its rich-text engine, ships experimental PostgreSQL, and spends a month fixing the fallout.
Leantime just landed 3.7, which replaced TinyMCE with a Tiptap-based editor across every rich-text surface, redesigned the wiki, and added experimental PostgreSQL support beside MySQL/MariaDB. The three follow-up patches in three weeks are real bug-fix work — PostgreSQL ROUND/GROUP BY errors, ticket PATCH 500s, session lifetime regressions — not cosmetic tidying. The team also pushed accessibility to WCAG 2.1 AA in the prior 3.6 line.
Leantime is mid-modernization: editor stack, database portability, and design-system tokens are all moving at once. The volume of PostgreSQL-specific bug fixes since 3.7.0 suggests Postgres is being driven by real users hitting real edges, not just a checklist item. Editor-related fixes show Tiptap migration is still settling in.
Expect 3.7.4 within a couple of weeks closing the remaining migration-era bugs, then a clearer 3.8 push around design-token rollout or PostgreSQL going non-experimental.
MeisterTask hardens enterprise muscle around workload planning while polishing daily team workflows.
MeisterTask is iterating on two parallel surfaces: the everyday task graph (checklist copy, blocked-dependency warnings, watchers-via-automation) and a deliberately upmarket workload tier (capacity planner gated to Enterprise, team workload widget gated to Business). The mix suggests retention work on lower-tier users while building a differentiated reason for admins to upgrade. Recent UX moves around the Home screen and Note tables show parallel investment in surface customization.
The workload planner is the directional bet — MeisterTask is positioning against tools like Asana and ClickUp for portfolio-level visibility, not just board-level task tracking. Smaller releases (custom fields in reports, automation-driven watchers, tables inside Note) cluster around making the same data exportable, reportable, and queryable. The arc is from task tracker toward a plannable team-operations layer.
Expect more reporting and cross-project view work to follow — likely resource-allocation extensions to the workload planner, plus deeper rollup support for the custom-field surface that's now reportable.
See more alternatives to Leantime →
See more alternatives to MeisterTask →