Loading content…
1. Listing metadata
Field-level data| Mria CRM | Issue History for Jira (Work Item History) | |
|---|---|---|
| Tagline | ||
| Description | ||
| Screenshots | — | — |
| Languages | ||
| Platforms | ||
| Developer | ||
| Listed | — | — |
| Last updated | — | — |
| Mria CRM | Issue History for Jira (Work Item History) | |
|---|---|---|
| Tagline | ||
| Description | ||
| Screenshots | — | — |
| Languages | ||
| Platforms | ||
| Developer | ||
| Listed | — | — |
| Last updated | — | — |
Get a report based on your workflow history in details, ordered by the date. Drill down to 'When', 'What' and 'Who' made the changes in work items during audits.
| Metric | Mria CRM | Issue History for Jira (Work Item History) |
|---|---|---|
| Rating | ★ 5.0 ★ | 4.7 ★ |
| Total reviews | 25 | ★ 95 |
| Active installs | 338+ | 3,109+ |
| Free plan | — | — |
| Pricing | From $2/yr | ★ From $0/yr |
| Pricing tiers | 6 tiers | 6 tiers |
| Listed features | 3 | 3 |
Based on the data on this page, Mria CRM is the stronger choice for most Atlassian Marketplace teams — 5.0★ vs Issue History for Jira (Work Item History)'s 4.7★ is a meaningful gap that usually reflects real product or support quality differences across the user base.
Pricing entry tiers: Mria CRM at From $2/yr, Issue History for Jira (Work Item History) at From $0/yr. 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.
Recommended by size: small/early-stage teams who need fast install and low risk should default to Mria CRM; mid-market and enterprise teams with specific feature requirements should evaluate both — Issue History for Jira (Work Item History)'s 95-review base may include the workflow context that matches your specific use case better than Mria CRM's broader-but-shallower coverage.
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 Atlassian 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: Mria CRM audit • Issue History for Jira (Work Item History) audit
Both Mria CRM and Issue History for Jira (Work Item History) offer paid plans only. Mria CRM starts at From $2/yr; Issue History for Jira (Work Item History) starts at From $0/yr. Compare the per-tier features in the Pricing section above before committing.
Mria CRM has the higher average rating (5.0★ from 25 reviews) compared to Issue History for Jira (Work Item History) (4.7★ from 95 reviews). Both are tracked daily by AppRanks, so the figures here update each refresh cycle.
Mria CRM holds the higher average rating (5.0★ vs 4.7★). That is the one dimension AppRanks can separate them on here — read both apps' detail pages for the feature breakdown and recent listing changes.
Both apps are one-click installs from the Atlassian Marketplace. Issue History for Jira (Work Item History) has the deeper published review base (95 vs 25), 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.
Mria CRM typically suits early-stage and growth-mode teams based on its published review base (25 reviews). Issue History for Jira (Work Item History) typically suits early-stage and growth-mode teams based on its published review base (95 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. Mria CRM and Issue History for Jira (Work Item History) 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 Mria CRM" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.