Leantime vs Atlassian
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.
Atlassian is repositioning Jira and Bitbucket as the orchestration substrate for outside coding agents.
Atlassian is shipping integrations that let third-party AI agents do work inside its products rather than competing with them. Cursor can now be assigned Jira issues directly, and Agentic Pipelines — launched a month ago with only the in-house Rovo Dev agent — now runs Claude Code as well. The surrounding blog content frames AI as a productivity tool whose business returns still depend on team coordination, a narrative that conveniently positions Atlassian's surfaces as the missing layer.
The bet is that Jira tickets and Bitbucket pipelines become the canonical task and run-time substrate for whichever coding agent the market settles on. Rovo Dev is being demoted from headline agent to one option among many, while Atlassian climbs to the orchestration layer above it. Expect the integration pattern (assign a work item to an agent ID, run an Agentic Pipeline with an agent of choice) to keep widening.
Next integrations are likely to follow the same template — another popular coding agent dropped into Agentic Pipelines, and more Jira surface area (sub-tasks, code review, support tickets) opened to assignment.
See more alternatives to Leantime →
See more alternatives to Atlassian →