Sleekplan
Sleekplan is making the public feedback board safe to run with real customers on it
A side-by-side editorial comparison of DoneDone and Request Tracker — release velocity, themes, recent moves, and the top alternatives to consider.
DoneDone just opened a door for other systems to file work without a human.
DoneDone has spent the year sanding down its task and conversation surfaces: Kanban sort options and collapsible columns, assignee filtering, checklist template reordering, tags in CSV exports. Most releases are small and explicitly credited to customer requests. Two recent moves break that pattern — Workflow Automations in early August, and now per-project email addresses that create tasks automatically.
Request Tracker maintains three branches in lockstep, and security is what sets the release calendar.
Best Practical ships RT across three concurrent branches, 4.4, 5.0 and 6.0, and coordinates security releases across all of them on the same day. The most recent pair, 5.0.10 and 6.0.3, both landed on 2026-05-20 carrying the same fixes: a privilege escalation and credential disclosure through the REST 2.0 user collection endpoint (CVE-2026-44231), SQL injection via the entry_aggregator parameter in JSON search (CVE-2026-41075), and an LDAP authentication bypass. Feature work rides along on the 6.0 branch, while 5.0 and 4.4 receive security fixes and little else.
DoneDone has spent the year sanding down its task and conversation surfaces: Kanban sort options and collapsible columns, assignee filtering, checklist template reordering, tags in CSV exports. Most releases are small and explicitly credited to customer requests. Two recent moves break that pattern — Workflow Automations in early August, and now per-project email addresses that create tasks automatically.
The product is moving from a place people manage work to a place work arrives and routes itself. Automations handle what happens when a task changes status; email intake handles how it gets created. Together they turn DoneDone into an endpoint other systems can drive, which matters more for its support and client-services users than any further board refinement.
The obvious next step is automation triggered by intake — routing rules on inbound email, or extending automations beyond status changes to assignment and escalation.
Best Practical ships RT across three concurrent branches, 4.4, 5.0 and 6.0, and coordinates security releases across all of them on the same day. The most recent pair, 5.0.10 and 6.0.3, both landed on 2026-05-20 carrying the same fixes: a privilege escalation and credential disclosure through the REST 2.0 user collection endpoint (CVE-2026-44231), SQL injection via the entry_aggregator parameter in JSON search (CVE-2026-41075), and an LDAP authentication bypass. Feature work rides along on the 6.0 branch, while 5.0 and 4.4 receive security fixes and little else.
The branch structure is consolidating. RT 4.4 reached its last planned release at 4.4.9 in October 2025, with users pointed at 5 or 6, and 6.0 is where features now land: dashboard saved searches gained pagination and sorting, statuses take colors from lifecycle configuration, custom fields display multi-column by default, and keyboard menu navigation improved. The 5.0 line still gets real work but of a narrower kind, such as the inline CSS handling in ticket history that shipped with 5.0.10. Expect the same-day multi-branch security release to remain the pattern for as long as two branches are supported.
The next release is most likely another coordinated security pair on 5.0 and 6.0, with feature work continuing to accumulate only on 6.0.
Other Support 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 DoneDone or Request Tracker.
Sleekplan is making the public feedback board safe to run with real customers on it
ServiceDesk Plus moved upstream of the ticket, then spent the week tidying the sidebar
Chatway's bot learned to read the store; now the store can listen back
ManageEngine's cloud service desk drips small fixes; its AI arrives data center by data center
Asset management is the real build; the feed is mostly an interview series.
Formbricks spends a whole RC train on making enterprise SSO stop breaking.
See all DoneDone alternatives → · See all Request Tracker alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. DoneDone 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. DoneDone 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 Support products to evaluate alongside.
Top DoneDone alternatives in Support are ranked by recent ship velocity. Browse the "DoneDone alternatives" section above for the current picks, or visit /alternatives/donedone for the full list with editorial commentary on each.
Top Request Tracker alternatives in Support are ranked by recent ship velocity. Browse the "Request Tracker alternatives" section above for the current picks, or visit /alternatives/request-tracker for the full list with editorial commentary on each.