Side-by-side comparison · 24 data points
Show a list of tickets with the same Custom Field value as current ticket
| Ticket History | Related Tickets by Custom Field | |
|---|---|---|
| Tagline | ||
| Description | ||
| Screenshots | images | images |
| Languages | ||
| Platforms | ||
| Developer | ||
| Listed | — | — |
| Last updated | — | — |
| Metric | Ticket History | Related Tickets by Custom Field |
|---|---|---|
| Rating | 4.0 ★ | 4.0 ★ |
| Total reviews | ★ 523 | 13 |
| Free plan | Yes | Yes |
| Pricing | Free | Free |
Ticket History and Related Tickets by Custom Field are evenly matched on rating (4.0★ vs 4.0★) — the differentiator comes down to pricing fit, feature breadth, and which app's interaction pattern suits your team's workflow.
Pricing entry tiers: Ticket History at Free, Related Tickets by Custom Field at Free. Check each app's tier structure for the capacity limits you actually need before deciding — the headline number is the same shape, but the gating shape per tier (seats, usage volume, integrations) varies.
Ticket History has the larger user base (523 reviews vs 13), which usually maps to broader integration coverage, faster bug-fix cadence, and a deeper bench of community workflow patterns. Related Tickets by Custom Field's smaller cohort can be an advantage for niche workflows where the bigger app has accumulated bloat.
Recommended evaluation path: install both apps' free tiers (where available) and run them in parallel on a small cohort for 7-14 days before committing. The data tables below show the per-feature breakdown — for most support teams the deciding factor will be a single integration or workflow detail that's hard to compare from listing pages alone.
This verdict is generated from the live marketplace data on this page — rating, review count, pricing tier, and category position all refresh from the canonical Zendesk Marketplace listing every 24 hours. AppRanks does not accept payment to influence comparison outcomes; the methodology is documented on the About page and applies identically to every pair on the site.
Read each app's audit: Ticket History audit • Related Tickets by Custom Field audit
Both Ticket History and Related Tickets by Custom Field offer paid plans only. Ticket History starts at Free; Related Tickets by Custom Field starts at Free. Compare the per-tier features in the Pricing section above before committing.
Ticket History (4.0★, 523 reviews) and Related Tickets by Custom Field (4.0★, 13 reviews) are essentially tied on rating. Look at review velocity and individual reviewer quotes — both visible on each app's detail page — to differentiate.
AppRanks cannot separate these two on rating — both sit at 4.0★. Ticket History does carry the larger published review base (523 vs 13). Read both apps' detail pages for the feature breakdown and recent listing changes.
Both apps are one-click installs from the Zendesk Marketplace. Ticket History has the deeper published review base (523 vs 13), which often — though not always — accompanies better-tested setup docs. AppRanks doesn't measure setup time directly: read the recent reviews on each app's detail page for user-reported install experience.
Ticket History typically suits early-stage and growth-mode teams based on its published review base (523 reviews). Related Tickets by Custom Field typically suits early-stage and growth-mode teams based on its published review base (13 reviews). A larger review base generally means the app has been exercised at scale — relevant if you are processing high volume or handling enterprise compliance requirements.
Migration support varies by app and category. Ticket History and Related Tickets by Custom Field both publish their export options on their marketplace listing pages (or in their support docs); some apps offer one-click import from competitors, others require CSV. The fastest check: search "import from Related Tickets by Custom Field" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.
