← 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 score5.00.0
Sparks · 30d00
Top themescustomer-support, shared-inbox, email-routing, custom-fieldsticketing, security-releases, multi-branch, cve
Last editorial update4d ago1mo ago
WebsiteVisit →Visit →

What is DoneDone?

DoneDone lets one email connection feed many Mailboxes, routed by filter priority.

DoneDone is a shared-inbox and task tool that has added structure in steps since August: workflow automations on status change, project tasks created from email, ten custom field types, and allow/block lists for connected mailboxes. The newest release lets one email connection serve several Mailboxes, with incoming mail routed to the first Mailbox whose filters accept it.

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
5.0

DoneDone lets one email connection feed many Mailboxes, routed by filter priority.

◆ Current state

DoneDone is a shared-inbox and task tool that has added structure in steps since August: workflow automations on status change, project tasks created from email, ten custom field types, and allow/block lists for connected mailboxes. The newest release lets one email connection serve several Mailboxes, with incoming mail routed to the first Mailbox whose filters accept it.

◆ Where it's heading

Most recent releases deepen email intake: project addresses in August, filters in September, shared connections with priority routing in October. Each builds on the last, turning a connected address into a rules-based router. Custom fields and automations add structure to what arrives, with releases landing every few weeks.

◆ Prediction

The filter-plus-priority model points toward richer routing rules, such as setting fields or assignees on arrival; the entries do not show that yet.

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. 5d agoDoneDoneNew: Use One Email Connection Across Multiple Mailboxes
  2. 25d agoDoneDoneUpdated Email Filters!
  3. 1mo agoDoneDoneCustom Fields are live! 🎉 ⚡
  4. 1mo agoDoneDoneCreate Project Tasks from Email!
  5. 2mo agoDoneDoneNew: Workflow Automations! ⚡
  6. 2mo agoDoneDoneInclude tags in CSV exports!
  7. 4mo agoRequest TrackerSecurity release fixes REST 2.0 credential disclosure and SQL injection
  8. 5mo agoRequest TrackerSame security fixes as 5.0.10, plus dashboard and accessibility work
  9. 0y agoRequest TrackerCalendar view for saved searches and memory management work
  10. 0y agoRequest TrackerCSV injection fix in TSV export, with assorted updates
  11. 0y 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 5.0 vs 0.0), with 0 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 5.0 vs 0.0), with 0 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.