ProdPad
ProdPad publishes weekly product-leadership essays and no release notes at all.
A side-by-side editorial comparison of Atlassian and OpenProject — release velocity, themes, recent moves, and the top alternatives to consider.
Atlassian now sells both halves of agent work: the index agents read and the intent they execute.
The Inside Atlassian feed mixes research posts and AI thought leadership with a steady run of real releases, and the releases have clustered on making the Teamwork Graph the context layer agents read from — Code Context for multi-repo codebase understanding, a Salesforce connector for account, opportunity and case data, agents operating inside Confluence and through the Rovo MCP. Jira Planner opens a second front. It targets intent rather than knowledge, on the argument that the bottleneck in AI-assisted development is not code generation but underspecified work: omit scope, architectural constraints and edge cases and the model fills the blanks itself.
OpenProject settles into patch work after 17.7 shipped resource management.
17.7.0 was the substantial release — a resource management module with departments and work schedules, pushing OpenProject past task tracking into staffing. The two releases since are patches. 17.7.2 fixes four bugs, among them project-level hourly rates that could not be adjusted and non-working days silently dropped when saved while a reschedule job was running — both in the scheduling and cost areas 17.7 had just expanded.
The Inside Atlassian feed mixes research posts and AI thought leadership with a steady run of real releases, and the releases have clustered on making the Teamwork Graph the context layer agents read from — Code Context for multi-repo codebase understanding, a Salesforce connector for account, opportunity and case data, agents operating inside Confluence and through the Rovo MCP. Jira Planner opens a second front. It targets intent rather than knowledge, on the argument that the bottleneck in AI-assisted development is not code generation but underspecified work: omit scope, architectural constraints and edge cases and the model fills the blanks itself.
Atlassian is competing on the substrate rather than the assistant, and it now claims both sides of it. One side widens what the Graph knows — repositories, CRM records, documents, tickets — with deliberately open agent surfaces in Confluence, Claude, Cursor and the IDE. The other side makes Jira the place where work is specified precisely enough for an agent to execute, which reframes the issue tracker from a record of what humans decided into the work order an agent runs against. The AI governance line is the third thread, selling oversight of agents customers already deploy.
Planner and Code Context are built to meet: expect a plan that resolves its own architectural constraints from the indexed codebase, and expect execution status to flow back into the Jira issue. More third-party systems should keep joining the Graph on the Salesforce pattern.
17.7.0 was the substantial release — a resource management module with departments and work schedules, pushing OpenProject past task tracking into staffing. The two releases since are patches. 17.7.2 fixes four bugs, among them project-level hourly rates that could not be adjusted and non-working days silently dropped when saved while a reschedule job was running — both in the scheduling and cost areas 17.7 had just expanded.
The release rhythm is a feature minor followed by a short tail of patches repairing the surface it just added, and this tail sits squarely in resource-management territory. Rate and non-working-day bugs are the predictable cost of shipping scheduling and cost tracking together. For self-hosted operators the advice does not change between these releases: take the patch.
Expect one or two more 17.7.x patches against the resource management surface before 17.8 opens a new feature line.
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 OpenProject.
ProdPad publishes weekly product-leadership essays and no release notes at all.
Aha! is threading one AI assistant through every product it owns, and giving it a screen of its own.
Teamhood's feed is an SEO comparison engine aimed at teams leaving other tools.
NocoBase back-ports its DeepSeek work to the 2.2.0 line and makes email sync survive a restart
A numbered performance program surfaces between the automated CI tags
Hostaway builds out the direct-booking stack while tightening who sees what
See all Atlassian alternatives → · See all OpenProject 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 6.3), with 2 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 2 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 OpenProject alternatives in PM are ranked by recent ship velocity. Browse the "OpenProject alternatives" section above for the current picks, or visit /alternatives/openproject for the full list with editorial commentary on each.