Atlassian
Atlassian is making Jira the ledger that AI coding agents write to
A side-by-side editorial comparison of NocoBase and Backlog — release velocity, themes, recent moves, and the top alternatives to consider.
The no-code platform is rebuilding itself around AI employees and Portals, in public, in alpha.
NocoBase is running two release trains at once: a 2.2 line still taking features and a 3.0 alpha series that has shipped eight builds in under two weeks. Nearly all the new surface in both lands in two subsystems — AI employees (assignable skills, scoped conversations, an embeddable chat block, frontend AI tools for JS blocks) and Portal manager (portal types, layouts, routing, access checks, backup). Client v2 is the third strand, with settings moving to a standalone app entry and v2 action settings catching up to v1.
Backlog ships steady Gantt and chart refinements, but the feed is mostly Nulab site furniture.
Only two entries in this window carry actual release content, and both are monthly digests: chart groups gaining a start/end date bar with issue counts and status breakdown on hover, personal charts dropping the parent-subtask relationship, an Android 3.0.1 redesign, Markdown in iOS custom-field text areas, plus quarterly-scale Gantt charts for Premium and Platinum plans and child-issue status filtering. The rest of the window is navigation, support links and marketing copy scraped from nulab.com — including rows that belong to sibling products Cacoo and Nulab Pass rather than to Backlog.
NocoBase is running two release trains at once: a 2.2 line still taking features and a 3.0 alpha series that has shipped eight builds in under two weeks. Nearly all the new surface in both lands in two subsystems — AI employees (assignable skills, scoped conversations, an embeddable chat block, frontend AI tools for JS blocks) and Portal manager (portal types, layouts, routing, access checks, backup). Client v2 is the third strand, with settings moving to a standalone app entry and v2 action settings catching up to v1.
The direction is a no-code builder turning into a host for AI workers rather than a form-and-table tool with AI bolted on. Skills built from plugins put AI employees on the same extensibility rail as everything else in the platform, and new installs now seed an AI portal by default, which is what moves it from feature to substrate. The alpha cadence — several builds a week, some tagged with nothing but a version bump — indicates this is being reshaped in the open rather than staged for one big cut.
Expect 3.0 to keep converging the AI employee and Portal subsystems until an AI portal is the default entry for a new instance, with client v2 reaching parity as the gate on leaving alpha. The entries do not indicate a target date for a stable 3.0.
Only two entries in this window carry actual release content, and both are monthly digests: chart groups gaining a start/end date bar with issue counts and status breakdown on hover, personal charts dropping the parent-subtask relationship, an Android 3.0.1 redesign, Markdown in iOS custom-field text areas, plus quarterly-scale Gantt charts for Premium and Platinum plans and child-issue status filtering. The rest of the window is navigation, support links and marketing copy scraped from nulab.com — including rows that belong to sibling products Cacoo and Nulab Pass rather than to Backlog.
The real work is concentrated on planning views — Gantt scale, chart grouping, issue filtering — and on closing gaps between the web app and the mobile clients. Several changes are explicitly gated to Premium and Platinum plans, so view sophistication is being used as tier differentiation. Nothing here suggests a change of direction; it is a mature tracker refining how work is visualised.
Given the run of chart and Gantt scale work, the next planning-view change is likely another axis of aggregation or filtering rather than a new surface. The scraped entries make cadence unreliable, so any stronger call would not be grounded.
Other PM products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either NocoBase or Backlog.
Atlassian is making Jira the ledger that AI coding agents write to
The public feed is a time-tracking SEO mill — comparison listicles, no product releases in sight.
Process Street's feed is a marketing blog; the only product signal is an already-shipped MCP server.
MeisterTask is wiring itself into AI assistants while filling in the admin features enterprises expect
monday.com is opening its board data to outside AI agents while grinding through admin gaps.
A local-first task manager quietly rebuilding itself into a sync engine with a plugin platform on top.
See all NocoBase alternatives → · See all Backlog alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NocoBase is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NocoBase is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
Top NocoBase alternatives in PM are ranked by recent ship velocity. Browse the "NocoBase alternatives" section above for the current picks, or visit /alternatives/nocobase for the full list with editorial commentary on each.
Top Backlog alternatives in PM are ranked by recent ship velocity. Browse the "Backlog alternatives" section above for the current picks, or visit /alternatives/backlog for the full list with editorial commentary on each.