← Back to home
Comparison · Support

DoneDone vs Request Tracker

A side-by-side editorial comparison of DoneDone and Request Tracker — release velocity, themes, recent moves, and the top alternatives to consider.

DoneDone vs Request Tracker: at a glance

FeatureDoneDoneRequest Tracker
SectorSupportSupport
Velocity score6.30.0
Sparks · 30d10
Top themestask-management, email-intake, workflow-automation, kanbanticketing, security-releases, multi-branch, cve
Last editorial update7d ago6d ago
WebsiteVisit →Visit →

What is DoneDone?

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.

Read the full DoneDone trajectory →

What is Request Tracker?

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.

Read the full Request Tracker trajectory →

DoneDone vs Request Tracker: editorial side-by-side

D
DoneDone
SUPPORT
6.3

DoneDone just opened a door for other systems to file work without a human.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

The obvious next step is automation triggered by intake — routing rules on inbound email, or extending automations beyond status changes to assignment and escalation.

R0.0

Request Tracker maintains three branches in lockstep, and security is what sets the release calendar.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to DoneDone and Request Tracker

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.

See all DoneDone alternatives → · See all Request Tracker alternatives →

Recent activity from DoneDone and Request Tracker

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 9d agoDoneDoneCreate Project Tasks from Email!
  2. 26d agoDoneDoneNew: Workflow Automations!
  3. 1mo agoDoneDoneInclude tags in CSV exports!
  4. 1mo agoDoneDoneChecklist Templates just got a little easier to manage.
  5. 2mo agoDoneDoneKanban Collapse Columns
  6. 3mo agoDoneDoneActions Are Now Hidden by Default
  7. 3mo agoRequest TrackerSecurity release fixes REST 2.0 credential disclosure and SQL injection
  8. 3mo agoRequest TrackerSame security fixes as 5.0.10, plus dashboard and accessibility work
  9. 10mo agoRequest TrackerCalendar view for saved searches and memory management work
  10. 10mo agoRequest TrackerCSV injection fix in TSV export, with assorted updates
  11. 10mo agoRequest TrackerFinal RT 4.4 release closes the branch with one security fix
  12. 1y agoRequest TrackerRelease exists mainly to support RTIR 6.0.1

Frequently asked questions

What is the difference between DoneDone and Request Tracker?

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.

Is DoneDone better than Request Tracker?

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.

What are the best alternatives to DoneDone?

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.

What are the best alternatives to Request Tracker?

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.