Sunsama vs OpenProject
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.
OpenProject leans into Jira migration and agile parity while absorbing a sustained bug-bounty wave
OpenProject is shipping aggressively across five maintained release branches simultaneously. 17.4 promotes the Jira Migrator out of feature-flag status with basic custom-field migration, and 17.3 reshapes the agile primitives — dedicated sprint objects, all action board types moved into the free Community edition, in-place project attribute editing, nested groups. The codebase is also absorbing a continuous stream of security disclosures (CVE-2026-44731 through -44736, GHSA-r85r, GHSA-hh5p, others) from an EU-sponsored YesWeHack bug bounty, with backported fixes landing across 16.6.x, 17.0.x, 17.1.x, 17.2.x, and 17.3.x on the same day as the headline release.
The dual focus — Jira parity (custom-field migration, sprint objects, flexible backlogs) and a deliberate Community-edition expansion (all action boards now free) — reads as a coordinated squeeze on Jira during Atlassian's Cloud-only migration push. The bug-bounty volume is unusual for a project this size and suggests OpenProject has crossed into enterprise-credibility scrutiny; the response pattern — same-day backports five branches deep — shows the maintainers treating security disclosures as cross-branch events by default.
The next minor release will likely round out the Jira Migrator — workflow and automation migration are the obvious next pieces given custom fields are now beta-complete. Continued public bounty intake will keep producing authorization and IDOR fixes; expect another coordinated cross-branch security cut within weeks.
See more alternatives to Sunsama →
See more alternatives to OpenProject →