Side-by-side comparison · 24 data points
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.
| ScriptRunner for Jira | AutoPage (Creates pages in Confluence with Jira issues) | |
|---|---|---|
| Tagline | ||
| Description | ||
| Screenshots | — | — |
| Languages | ||
| Platforms | ||
| Developer | ||
| Listed | — | — |
| Last updated | — |
Create a rule and update Confluence pages from Jira issues and populate user defined templates with Jira issue data. Use our flexible automation rules to realize bi-directional synchronization for documentation purpose.
| Metric | ScriptRunner for Jira | AutoPage (Creates pages in Confluence with Jira issues) |
|---|---|---|
| Rating | 4.6 ★ | ★ 5.0 ★ |
| Total reviews | ★ 826 | 15 |
| Active installs | 35,011+ | 161+ |
| Free plan | — | — |
| Pricing | From $0/yr | From $0/yr |
| Pricing tiers | 6 tiers | 6 tiers |
| Listed features | 3 | 3 |
Based on the data on this page, AutoPage (Creates pages in Confluence with Jira issues) is the stronger choice for most Atlassian Marketplace teams — 5.0★ vs ScriptRunner for Jira's 4.6★ is a meaningful gap that usually reflects real product or support quality differences across the user base.
Pricing entry tiers: ScriptRunner for Jira at From $0/yr, AutoPage (Creates pages in Confluence with Jira issues) 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 15), which usually maps to broader integration coverage, faster bug-fix cadence, and a deeper bench of community workflow patterns. AutoPage (Creates pages in Confluence with Jira issues)'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 AutoPage (Creates pages in Confluence with Jira issues); mid-market and enterprise teams with specific feature requirements should evaluate both — ScriptRunner for Jira's 826-review base may include the workflow context that matches your specific use case better than AutoPage (Creates pages in Confluence with Jira issues)'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: ScriptRunner for Jira audit • AutoPage (Creates pages in Confluence with Jira issues) audit
| Keyword | ScriptRunner for Jira | AutoPage (Creates pages in Confluence with Jira issues) |
|---|---|---|
| forms | #106 | #380 |
| form | #213 | #491 |
Both ScriptRunner for Jira and AutoPage (Creates pages in Confluence with Jira issues) offer paid plans only. ScriptRunner for Jira starts at From $0/yr; AutoPage (Creates pages in Confluence with Jira issues) starts at From $0/yr. Compare the per-tier features in the Pricing section above before committing.
AutoPage (Creates pages in Confluence with Jira issues) has the higher average rating (5.0★ from 15 reviews) compared to ScriptRunner for Jira (4.6★ from 826 reviews). Both are tracked daily by AppRanks, so the figures here update each refresh cycle.
AutoPage (Creates pages in Confluence with Jira issues) holds the higher average rating (5.0★ vs 4.6★). 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 15), 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.
ScriptRunner for Jira typically suits early-stage and growth-mode teams based on its published review base (826 reviews). AutoPage (Creates pages in Confluence with Jira issues) typically suits early-stage and growth-mode teams based on its published review base (15 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. ScriptRunner for Jira and AutoPage (Creates pages in Confluence with Jira issues) 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 AutoPage (Creates pages in Confluence with Jira issues)" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.