Atlassian
Rovo reaches into Drive and SharePoint while the app ecosystem runs down the Connect clock.
A side-by-side editorial comparison of Phorge and Asana — release velocity, themes, recent moves, and the top alternatives to consider.
Phorge tags a release per fix, and years pass between the ones that reach this feed.
Phorge, the community continuation of Phabricator, tags releases named for the week they land and for the single change they carry. The entries visible here span three years and are all small defensive fixes: query errors instead of raw exceptions on malformed task IDs, a readable error screen when configuration fails to load, an empty authored date on Subversion commits, a crash in a commit hook when getenv returns false.
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.
Phorge, the community continuation of Phabricator, tags releases named for the week they land and for the single change they carry. The entries visible here span three years and are all small defensive fixes: query errors instead of raw exceptions on malformed task IDs, a readable error screen when configuration fails to load, an empty authored date on Subversion commits, a crash in a commit hook when getenv returns false.
This is a project in stewardship rather than development. The work concentrates on the places an inherited codebase breaks — Subversion paths that upstream barely exercised, error handling that assumed configuration always loads, exception types leaking to users — and each fix is documented with a reproduction and test plan in the old Phabricator review style. Nothing in this window suggests new capability; the goal visible in the changelog is that the software keeps running for the installs that already depend on it.
The pattern points to more individually tagged small fixes in legacy code paths and error handling; there is no signal here of a larger release being assembled.
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.
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 Phorge or Asana.
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.
Zoho Projects makes time tracking the product's center of gravity, and lets Zia build the schema.
Jira is being pushed upward — from tracking the work to judging its cost, risk and business health.
Steady small-surface polish across Basecamp and HEY, with no directional move.
See all Phorge alternatives → · See all Asana alternatives →
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 Phorge alternatives in PM are ranked by recent ship velocity. Browse the "Phorge alternatives" section above for the current picks, or visit /alternatives/phorge for the full list with editorial commentary on each.
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.