NocoBase
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
A side-by-side editorial comparison of Atlassian and Backlog — release velocity, themes, recent moves, and the top alternatives to consider.
Atlassian keeps feeding the Teamwork Graph — Salesforce is the newest source agents can read.
The Inside Atlassian feed mixes research posts and AI thought leadership with a steady run of real releases, and the releases cluster on one idea: making the Teamwork Graph the context layer agents read from. Code Context brought multi-repo codebase understanding into it, a Salesforce connector now brings account, opportunity and case data, and agents already operate inside Confluence and through the Rovo MCP.
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.
The Inside Atlassian feed mixes research posts and AI thought leadership with a steady run of real releases, and the releases cluster on one idea: making the Teamwork Graph the context layer agents read from. Code Context brought multi-repo codebase understanding into it, a Salesforce connector now brings account, opportunity and case data, and agents already operate inside Confluence and through the Rovo MCP.
Atlassian is competing on the index rather than the assistant. Each release widens what the Graph knows — repositories, CRM records, documents, service tickets — and the agent surfaces are deliberately open, running in Confluence, in Claude, in Cursor, in the IDE. Alongside that, the AI governance line signals a second front: selling oversight of the agents customers are already deploying.
Expect more third-party systems connected into the Teamwork Graph on the Salesforce pattern, and governance packaged as a product rather than a posture.
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 Atlassian or Backlog.
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
Hive ships in batches, and this one is all planning accuracy and admin control.
Plane ships a fortnightly digest, and the AI layer is where the real work is going.
Ever Teams shipped ten tags in twelve hours and one of them touched the product
Asana's agent left the app — it now answers work questions inside Slack threads.
Apploye's feed is an SEO blog, and its running theme is defending monitoring on privacy grounds.
See all Atlassian 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. Atlassian is currently shipping more aggressively (velocity 10.0 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. Atlassian is currently shipping more aggressively (velocity 10.0 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 Atlassian alternatives in PM are ranked by recent ship velocity. Browse the "Atlassian alternatives" section above for the current picks, or visit /alternatives/atlassian 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.