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 | Time in Status report, Cycle Time & Lead Time Chart for Jira | |
|---|---|---|
| Tagline | ||
| Description | ||
| Screenshots | — | — |
| Languages | ||
| Platforms | ||
| Developer | ||
| Listed | — | — |
| Last updated | — | — |
Time in Status Reports/Average Time in status/Time to resolution, Trend, Cycle time and Lead time gadgets/charts on Jira Dashboard
| Metric | ScriptRunner for Jira | Time in Status report, Cycle Time & Lead Time Chart for Jira |
|---|---|---|
| Rating | 3.7 ★ | ★ 4.0 ★ |
| Total reviews | ★ 819 | 5 |
| Active installs | 36,489+ | 807+ |
| Free plan | — | — |
| Pricing | From $0/yr | — |
| Built for Shopify | — | — |
| Pricing tiers | 6 tiers | — |
| Listed features | 3 | — |
Time in Status report, Cycle Time & Lead Time Chart for Jira edges out ScriptRunner for Jira on rating (4.0★ vs 3.7★), but the gap is small enough that pricing fit and feature differentiation should drive the decision more than the headline number. ScriptRunner for Jira has the larger user base (819 reviews vs 5), which usually maps to broader integration coverage, faster bug-fix cadence, and a deeper bench of community workflow patterns. Time in Status report, Cycle Time & Lead Time Chart for Jira's smaller cohort can be an advantage for niche workflows where the bigger app has accumulated bloat. Recommended by store size: small/early-stage merchants who need fast install and low risk should default to Time in Status report, Cycle Time & Lead Time Chart for Jira; mid-market and enterprise merchants with specific feature requirements should evaluate both — ScriptRunner for Jira's 819-review base may include the workflow context that matches your specific use case better than Time in Status report, Cycle Time & Lead Time Chart 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: ScriptRunner for Jira audit • Time in Status report, Cycle Time & Lead Time Chart for Jira audit
No features listed.
| Keyword | ScriptRunner for Jira | Time in Status report, Cycle Time & Lead Time Chart for Jira |
|---|---|---|
| time | Not ranked | #8 |
| forms | #101 | Not ranked |
| form | #198 | Not ranked |
No tracked changes.
No description available.
Time in Status report, Cycle Time & Lead Time Chart for Jira has the higher average rating (4.0★ from 5 reviews) compared to ScriptRunner for Jira (3.7★ from 819 reviews). Both are tracked daily by AppRanks, so the figures here update each refresh cycle.
It depends on what you're optimizing for. ScriptRunner for Jira fits better if you prioritize broader integrations; Time in Status report, Cycle Time & Lead Time Chart for Jira is the call if you need the higher-rated option. Read both apps' detail pages on AppRanks for the full feature breakdown, install counts, and recent listing changes.
Both apps are one-click installs from the Atlassian Marketplace marketplace. ScriptRunner for Jira has more onboarding documentation maturity (819 reviews vs 5), which usually translates to better-tested setup wizards and quicker time-to-value. AppRanks doesn't measure setup time directly — read the recent reviews on each app's detail page for merchant-reported install experience.
ScriptRunner for Jira typically suits early-stage and growth-mode stores based on its review-base composition (819 reviews). Time in Status report, Cycle Time & Lead Time Chart for Jira aligns more with early-stage and growth-mode stores (5 reviews). Larger review bases generally mean the app has been load-tested at scale — relevant if you're processing high order volume or handling enterprise compliance requirements.
Migration support varies by app and category. ScriptRunner for Jira and Time in Status report, Cycle Time & Lead Time Chart 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 Time in Status report, Cycle Time & Lead Time Chart for Jira" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.