Sunsama vs Jira
Side-by-side trajectory, velocity, and editorial themes.
Sunsama ships Task Priority + Auto-Sort and starts wiring Sunny into MCP — daily planning gets opinionated.
Sunsama is in steady weekly-release cadence, with the bulk of recent work concentrated in two places: the Task Priority + Auto-Sort system, which has just graduated from beta into a documented core feature, and the Sunny AI assistant, which is gaining persistent memory and MCP-callable primitives like get_task_by_id. The integration surface continues to deepen — Linear, Todoist, Jira, Asana imports now carry priority signal through into Sunsama's own model.
The product is moving from 'manual daily planner' toward 'opinionated planner that can be driven by Sunny or external agents.' Auto-Sort is the most telling move: Sunsama is now willing to reorder the user's day on its own based on priority and scheduled time, which is a philosophical step away from the manual drag-and-drop heritage. The MCP work signals they want Sunsama to be addressable by other AI tools — not just consumed via the Sunny UI.
Expect the next few weekly drops to expand Sunny's MCP toolset (write actions, not just reads) and to roll priority rollover into more of the integration importers. A 'Sunny plans your day' end-to-end flow that leans on the new priority + auto-sort plumbing is the natural next milestone.
Atlassian is quietly turning Jira into the connective tissue for an AI-driven enterprise work platform.
Jira keeps shipping along two tracks at once. One is enterprise lifecycle plumbing — sandbox-to-production config promotion, guest access on paid plans, multi-space service queues — that closes long-standing change-management and collaboration gaps. The other is platform expansion: HRIS data flowing into the Atlassian Teamwork Graph, Rovo skills landing inside Jira Align, and Bitbucket merge queues.
The center of gravity is moving from issue tracking to a unified work platform with AI on top of an enriching Teamwork Graph. Atlassian is treating the Graph as the substrate Rovo reasons over, and is now feeding it HRIS data — well beyond traditional Jira scope. Enterprise-grade controls (sandbox promotion, guest seats, multi-space views) are being assembled in parallel to make that platform pitch defensible at the CIO level.
Expect more first-party connectors that load non-Jira data (HRIS, CRM, finance) into the Teamwork Graph, paired with Rovo skills that act on it. Configuration Promotion should reach GA within a quarter.
See more alternatives to Sunsama →
See more alternatives to Jira →