Atlassian
Rovo reaches into Drive and SharePoint while the app ecosystem runs down the Connect clock.
A side-by-side editorial comparison of NocoBase and Jira — release velocity, themes, recent moves, and the top alternatives to consider.
NocoBase is running two release trains at once and putting AI employees inside the apps you build.
NocoBase is publishing 2.2 and 3.0 pre-releases in parallel, often hours apart, and the same pull request frequently appears in both — the AI chat box block shows up in a 2.2 alpha and a 2.2 beta on consecutive days. The 3.0 line is dominated by Portal manager work: fixed layouts, an application-wide default portal, AI-mode portals with their own backup and restore path. The 2.2 line is where the AI employees feature is landing, alongside client v2 and approval workflow refinements.
Jira is being pushed upward — from tracking the work to judging its cost, risk and business health.
Atlassian's recent Jira and Jira Service Management entries cluster around two ideas: giving leaders a synthesized view of delivery, and giving Rovo something operational to do. Alongside sit connector and consolidation items — HRIS ingestion into the Teamwork Graph, dashboards relocating into an Analytics app.
NocoBase is publishing 2.2 and 3.0 pre-releases in parallel, often hours apart, and the same pull request frequently appears in both — the AI chat box block shows up in a 2.2 alpha and a 2.2 beta on consecutive days. The 3.0 line is dominated by Portal manager work: fixed layouts, an application-wide default portal, AI-mode portals with their own backup and restore path. The 2.2 line is where the AI employees feature is landing, alongside client v2 and approval workflow refinements.
The direction is AI as a building block rather than an assistant bolted to the admin UI. An embeddable chat box block with scoped conversations, frontend AI tools callable from JS blocks, a knowledge base with configurable vector databases, and a plugin development guide for defining AI employee tools and skills all point the same way: NocoBase wants the apps its users assemble to contain AI employees, not just be administered by one. The parallel trains are the cost of doing that while a 3.0 platform rework is in flight.
Expect 3.0 to stabilise the Portal manager as the shell that AI-mode applications run inside, with the AI employee work merging forward from 2.2 rather than being rebuilt. The alpha releases carrying no notes at all make the actual 3.0 scope hard to read from the changelog.
Atlassian's recent Jira and Jira Service Management entries cluster around two ideas: giving leaders a synthesized view of delivery, and giving Rovo something operational to do. Alongside sit connector and consolidation items — HRIS ingestion into the Teamwork Graph, dashboards relocating into an Analytics app.
The tracker is becoming a decision surface. Strategic Intelligence and the AI Incident Prevention Center both take data Jira already holds and turn it into judgments — cost of delivery, change risk, recurring-incident causes — rather than views. The connector and dashboard moves are the plumbing that makes those judgments possible across products.
Expect more Rovo-driven surfaces that read across work, goals and talent in one place, and continued consolidation of overlapping analytics entry points into the Analytics app.
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 Jira.
Rovo reaches into Drive and SharePoint while the app ecosystem runs down the Connect clock.
The time-tracking product is invisible behind a steady run of comparison roundups.
Wakapi is quietly rebuilding itself around the login and container requirements teams ask for.
Phorge tags a release per fix, and years pass between the ones that reach this feed.
Zoho Projects makes time tracking the product's center of gravity, and lets Zia build the schema.
Steady small-surface polish across Basecamp and HEY, with no directional move.
See all NocoBase alternatives → · See all Jira 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 Jira alternatives in PM are ranked by recent ship velocity. Browse the "Jira alternatives" section above for the current picks, or visit /alternatives/jira for the full list with editorial commentary on each.