Wakapi
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
A side-by-side editorial comparison of Atlassian and ProWorkflow — 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.
ProWorkflow telegraphs a roadmap, not a release.
The recent feed isn't shipped features — it's a 'Fix the Chain' roadmap series posted in March–April 2026, restating a multi-year initiative to better connect the quote → project → invoice stages. Highlights: line items at the project level (so non-time materials have a home), part-invoicing improvements, recurring invoice flow, custom layouts, and gross-margin / cost visibility. The 2023-07-16 entry is the original 'From there to here' framing post being re-surfaced.
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.
The recent feed isn't shipped features — it's a 'Fix the Chain' roadmap series posted in March–April 2026, restating a multi-year initiative to better connect the quote → project → invoice stages. Highlights: line items at the project level (so non-time materials have a home), part-invoicing improvements, recurring invoice flow, custom layouts, and gross-margin / cost visibility. The 2023-07-16 entry is the original 'From there to here' framing post being re-surfaced.
ProWorkflow is in a re-explanation phase: telling existing customers what it intends to fix structurally, rather than announcing what it just shipped. The thesis — close the data gaps between quote/project/invoice so financial insight is end-to-end — is coherent but slow. There's a notable gap between the 2023 framing post and the 2026 follow-ups, suggesting the project moved slowly or the comms went quiet for a stretch.
If 'Fix the Chain' is real, the next visible signal will be a line-items-on-projects feature actually shipping, followed by part-invoicing and recurring-invoice tooling. If those don't appear within the next 6 entries, the roadmap is likely outpacing engineering capacity and customers should expect more narrative than delivery.
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 ProWorkflow.
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 ProWorkflow 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.8), 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.8), 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 ProWorkflow alternatives in PM are ranked by recent ship velocity. Browse the "ProWorkflow alternatives" section above for the current picks, or visit /alternatives/proworkflow for the full list with editorial commentary on each.