Wakapi
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
A side-by-side editorial comparison of Jira and OpenProject — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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 Jira or OpenProject.
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 Jira 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. OpenProject 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. OpenProject 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 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.
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.