Wakapi
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
A side-by-side editorial comparison of Atlassian and Resource Guru — 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.
Resource Guru is opening the schedule up — first to AI tools, now to bookings that fit themselves.
Resource Guru publishes real product notes and SEO articles through the same feed, so the signal has to be separated from capacity-planning guides and review round-ups. The product entries are short — 200 to 320 characters — but they are genuine launches, not excerpts of something larger. Recent releases cluster around two things: making the schedule readable on the user's own terms (custom field colors, configurable Projects columns, placeholder digests) and making it reachable by machines, via an MCP server and integrations with Trello and ClickUp.
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.
Resource Guru publishes real product notes and SEO articles through the same feed, so the signal has to be separated from capacity-planning guides and review round-ups. The product entries are short — 200 to 320 characters — but they are genuine launches, not excerpts of something larger. Recent releases cluster around two things: making the schedule readable on the user's own terms (custom field colors, configurable Projects columns, placeholder digests) and making it reachable by machines, via an MCP server and integrations with Trello and ClickUp.
Custom fields have become the organizing spine of the product — they now drive color coding and column layout rather than sitting as inert metadata. Alongside that, the scheduling engine is taking on decisions the user used to make manually: placeholder digests surface unassigned work, and Total Hours bookings hand the system a quantity and a window instead of fixed slots. The MCP server points the same schedule data at AI assistants. The through-line is a resource scheduler that increasingly arranges work rather than just recording it.
Total Hours bookings put allocation logic inside the scheduler for the first time, and the MCP server exposes account data to assistants that could drive it; the next step these entries point toward is more scheduling decisions being automated rather than displayed. What is not visible yet is whether the MCP server will gain write access or stay read-only.
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 Resource Guru.
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
Process Street's public feed is an SEO content engine, not a changelog.
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
See all Atlassian alternatives → · See all Resource Guru alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — integrations — within PM. Atlassian is currently shipping more aggressively (velocity 10.0 vs 6.3), with 1 editorial sparks in the last 30 days against 1. 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 6.3), with 1 editorial sparks in the last 30 days against 1. 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 Resource Guru alternatives in PM are ranked by recent ship velocity. Browse the "Resource Guru alternatives" section above for the current picks, or visit /alternatives/resourceguru for the full list with editorial commentary on each.