Atlassian
Rovo reaches into Drive and SharePoint while the app ecosystem runs down the Connect clock.
A side-by-side editorial comparison of Asana and Jira — release velocity, themes, recent moves, and the top alternatives to consider.
AI Teammates get a skills library while the core work surface quietly gets fixed.
Asana is shipping on two tracks at once. The agentic track is moving fast: AI Teammates gained a Skills Library of specialized capabilities, then the ability to read, create, and update project rules with a review step before publishing, while AI Studio began critiquing the rule instructions users write. The second track is long-overdue core work — threaded task comments went live, Notes was rebuilt and renamed Pages, and subtask view controls landed in the task pane.
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.
Asana is shipping on two tracks at once. The agentic track is moving fast: AI Teammates gained a Skills Library of specialized capabilities, then the ability to read, create, and update project rules with a review step before publishing, while AI Studio began critiquing the rule instructions users write. The second track is long-overdue core work — threaded task comments went live, Notes was rebuilt and renamed Pages, and subtask view controls landed in the task pane.
The AI Teammates architecture is becoming composable rather than monolithic: start from a role-shaped teammate, attach skills, then let it operate on the automation layer itself. That last step matters — an agent that writes and edits rules is acting on the system that runs the work, not just on tasks inside it, and Asana has consistently gated it behind human review. Meanwhile the base product is closing gaps that predate any of this, which suggests the AI work is not consuming the whole roadmap.
Expect the Skills Library to open to customer-authored or third-party skills, and expect the review step on agent-generated rules to become the template for wider write access.
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 Asana 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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Asana 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. Asana 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 Asana alternatives in PM are ranked by recent ship velocity. Browse the "Asana alternatives" section above for the current picks, or visit /alternatives/asana 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.