Side-by-side comparison · 24 data points
My Requests Extension for Jira Service Management gives you control over the Requests page with configurable fields, saved filters, user scopes, export options, and "View as" functionality. It enhances visibility, usability, and access for end users.
| My Requests Extension for Jira Service Management | ScriptRunner for Jira | |
|---|---|---|
| Tagline | ||
| Description | ||
| Screenshots | — | — |
| Languages | ||
| Platforms | ||
| Developer | ||
| Listed | — | — |
| Last updated |
ScriptRunner is the top scripting, automation and customisation app: Automate workflows, build custom fields and integrations with Groovy scripts and enhanced JQL. Execute admin and workflow functions without having to write a complete add-on.
| Metric | My Requests Extension for Jira Service Management | ScriptRunner for Jira |
|---|---|---|
| Rating | 4.5 ★ | ★ 4.6 ★ |
| Total reviews | 34 | ★ 826 |
| Active installs | 1,502+ | 35,011+ |
| Free plan | — | — |
| Pricing | From $0/yr | From $0/yr |
| Pricing tiers | 6 tiers | 6 tiers |
| Listed features | 3 | 3 |
ScriptRunner for Jira edges out My Requests Extension for Jira Service Management on rating (4.6★ vs 4.5★), but the gap is small enough that pricing fit and feature differentiation should drive the decision more than the headline number.
Pricing entry tiers: My Requests Extension for Jira Service Management at From $0/yr, ScriptRunner for Jira 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.
ScriptRunner for Jira has the larger user base (826 reviews vs 34), which usually maps to broader integration coverage, faster bug-fix cadence, and a deeper bench of community workflow patterns. My Requests Extension for Jira Service Management's smaller cohort can be an advantage for niche workflows where the bigger app has accumulated bloat.
Recommended by size: small/early-stage teams who need fast install and low risk should default to ScriptRunner for Jira; mid-market and enterprise teams with specific feature requirements should evaluate both — My Requests Extension for Jira Service Management's 34-review base may include the workflow context that matches your specific use case better than ScriptRunner for Jira'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: My Requests Extension for Jira Service Management audit • ScriptRunner for Jira audit
| — |
| Keyword | My Requests Extension for Jira Service Management | ScriptRunner for Jira |
|---|---|---|
| forms | Not ranked | #106 |
| form | Not ranked | #213 |
Both My Requests Extension for Jira Service Management and ScriptRunner for Jira offer paid plans only. My Requests Extension for Jira Service Management starts at From $0/yr; ScriptRunner for Jira starts at From $0/yr. Compare the per-tier features in the Pricing section above before committing.
ScriptRunner for Jira has the higher average rating (4.6★ from 826 reviews) compared to My Requests Extension for Jira Service Management (4.5★ from 34 reviews). Both are tracked daily by AppRanks, so the figures here update each refresh cycle.
ScriptRunner for Jira holds the higher average rating (4.6★ vs 4.5★). 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. ScriptRunner for Jira has the deeper published review base (826 vs 34), 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.
My Requests Extension for Jira Service Management typically suits early-stage and growth-mode teams based on its published review base (34 reviews). ScriptRunner for Jira typically suits early-stage and growth-mode teams based on its published review base (826 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. My Requests Extension for Jira Service Management and ScriptRunner for Jira 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 My Requests Extension for Jira Service Management" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.